why there is no the "binlogs" directory after milvus-backup #38279

hxlsky · 2024-12-06T07:30:14Z

hxlsky
Dec 6, 2024

i backup milvus in k8s:
/opt/milvus_backup/milvus-backup create -n mytest_bak_20241206 -d mvsdb_ai --config=/opt/milvus_backup/conf/backup.yaml

and i can not see the "binlogs" directory in the minio backup directory
[root@ceph02 mytest_bak_20241206]# pwd
/data/minio/data/a-bucket/backup/mytest_bak_20241206
[root@ceph02 mytest_bak_20241206]# ls
meta

just only the meta directory,so i can not restore the database.

error just as flowing:

[2024/12/06 15:18:27.962 +08:00] [INFO] [core/backup_impl_restore_backup.go:746] ["execute bulk insert"] [db=mvsdb_ai] [collection=tb_01] [partition=_default] [files="[backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072]"] [endTime=454418600420704258]
[2024/12/06 15:18:27.987 +08:00] [ERROR] [core/backup_impl_restore_backup.go:760] ["fail to bulk insert"] [db=mvsdb_ai] [collectionName=tb_01] [partitionName=_default] [files="[backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072]"] [error="no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed"] [errorVerbose="no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed\n(1) attached stack trace\n -- stack trace:\n | github.com/milvus-io/milvus-sdk-go/v2/client.handleRespStatus\n | \t/home/runner/go/pkg/mod/github.com/wayblink/milvus-sdk-go/v2@v2.3.0-beta4.0.20240814024750-1d41342d2c27/client/collection.go:39\n | github.com/milvus-io/milvus-sdk-go/v2/client.(*GrpcClient).BulkInsert\n | \t/home/runner/go/pkg/mod/github.com/wayblink/milvus-sdk-go/v2@v2.3.0-beta4.0.20240814024750-1d41342d2c27/client/insert.go:416\n | github.com/zilliztech/milvus-backup/core.(*MilvusClient).BulkInsert\n | \t/home/runner/work/milvus-backup/milvus-backup/core/milvus_sdk_wrapper.go:124\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeBulkInsert\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:757\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func3\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:591\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func8\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:710\n | github.com/zilliztech/milvus-backup/internal/common.(*WorkerPool).work.func1\n | \t/home/runner/work/milvus-backup/milvus-backup/internal/common/workerpool.go:70\n | golang.org/x/sync/errgroup.(*Group).Go.func1\n | \t/home/runner/go/pkg/mod/golang.org/x/sync@v0.3.0/errgroup/errgroup.go:75\n | runtime.goexit\n | \t/opt/hostedtoolcache/go/1.18.10/x64/src/runtime/asm_amd64.s:1571\nWraps: (2) no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed\nError types: (1) *withstack.withStack (2) *errutil.leafError"] [stack="github.com/zilliztech/milvus-backup/core.(*BackupContext).executeBulkInsert\n\t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:760\ngithub.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func3\n\t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:591\ngithub.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func8\n\t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:710\ngithub.com/zilliztech/milvus-backup/internal/common.(*WorkerPool).work.func1\n\t/home/runner/work/milvus-backup/milvus-backup/internal/common/workerpool.go:70\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\t/home/runner/go/pkg/mod/golang.org/x/sync@v0.3.0/errgroup/errgroup.go:75"]
[2024/12/06 15:18:27.988 +08:00] [ERROR] [core/backup_impl_restore_backup.go:710] ["fail to bulk insert to partition"] [backup_db_name=mvsdb_ai] [backup_collection_name=mvsdb_ai] [target_db_name=mvsdb_ai] [target_collection_name=tb_01] [skipDiskQuotaCheck=false] [partition=_default] [error="no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed"] [errorVerbose="no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed\n(1) attached stack trace\n -- stack trace:\n | github.com/milvus-io/milvus-sdk-go/v2/client.handleRespStatus\n | \t/home/runner/go/pkg/mod/github.com/wayblink/milvus-sdk-go/v2@v2.3.0-beta4.0.20240814024750-1d41342d2c27/client/collection.go:39\n | github.com/milvus-io/milvus-sdk-go/v2/client.(*GrpcClient).BulkInsert\n | \t/home/runner/go/pkg/mod/github.com/wayblink/milvus-sdk-go/v2@v2.3.0-beta4.0.20240814024750-1d41342d2c27/client/insert.go:416\n | github.com/zilliztech/milvus-backup/core.(*MilvusClient).BulkInsert\n | \t/home/runner/work/milvus-backup/milvus-backup/core/milvus_sdk_wrapper.go:124\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeBulkInsert\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:757\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func3\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:591\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func8\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:710\n | github.com/zilliztech/milvus-backup/internal/common.(*WorkerPool).work.func1\n | \t/home/runner/work/milvus-backup/milvus-backup/internal/common/workerpool.go:70\n | golang.org/x/sync/errgroup.(*Group).Go.func1\n | \t/home/runner/go/pkg/mod/golang.org/x/sync@v0.3.0/errgroup/errgroup.go:75\n | runtime.goexit\n | \t/opt/hostedtoolcache/go/1.18.10/x64/src/runtime/asm_amd64.s:1571\nWraps: (2) no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed\nError types: (1) *withstack.withStack (2) *errutil.leafError"] [stack="github.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func8\n\t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:710\ngithub.com/zilliztech/milvus-backup/internal/common.(*WorkerPool).work.func1\n\t/home/runner/work/milvus-backup/milvus-backup/internal/common/workerpool.go:70\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\t/home/runner/go/pkg/mod/golang.org/x/sync@v0.3.0/errgroup/errgroup.go:75"]
[2024/12/06 15:18:27.988 +08:00] [ERROR] [core/backup_impl_restore_backup.go:359] ["executeRestoreCollectionTask failed"] [TargetDBName=mvsdb_ai] [TargetCollectionName=tb_01] [error="no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed"] [errorVerbose="no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed\n(1) attached stack trace\n -- stack trace:\n | github.com/milvus-io/milvus-sdk-go/v2/client.handleRespStatus\n | \t/home/runner/go/pkg/mod/github.com/wayblink/milvus-sdk-go/v2@v2.3.0-beta4.0.20240814024750-1d41342d2c27/client/collection.go:39\n | github.com/milvus-io/milvus-sdk-go/v2/client.(*GrpcClient).BulkInsert\n | \t/home/runner/go/pkg/mod/github.com/wayblink/milvus-sdk-go/v2@v2.3.0-beta4.0.20240814024750-1d41342d2c27/client/insert.go:416\n | github.com/zilliztech/milvus-backup/core.(*MilvusClient).BulkInsert\n | \t/home/runner/work/milvus-backup/milvus-backup/core/milvus_sdk_wrapper.go:124\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeBulkInsert\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:757\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func3\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:591\n | github.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreCollectionTask.func8\n | \t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:710\n | github.com/zilliztech/milvus-backup/internal/common.(*WorkerPool).work.func1\n | \t/home/runner/work/milvus-backup/milvus-backup/internal/common/workerpool.go:70\n | golang.org/x/sync/errgroup.(*Group).Go.func1\n | \t/home/runner/go/pkg/mod/golang.org/x/sync@v0.3.0/errgroup/errgroup.go:75\n | runtime.goexit\n | \t/opt/hostedtoolcache/go/1.18.10/x64/src/runtime/asm_amd64.s:1571\nWraps: (2) no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed\nError types: (1) *withstack.withStack (2) *errutil.leafError"] [stack="github.com/zilliztech/milvus-backup/core.(*BackupContext).executeRestoreBackupTask.func1\n\t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:359\ngithub.com/zilliztech/milvus-backup/internal/common.(*WorkerPool).work.func1\n\t/home/runner/work/milvus-backup/milvus-backup/internal/common/workerpool.go:70\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\t/home/runner/go/pkg/mod/golang.org/x/sync@v0.3.0/errgroup/errgroup.go:75"]
[2024/12/06 15:18:27.989 +08:00] [ERROR] [core/backup_impl_restore_backup.go:323] ["execute restore collection fail"] [backupId=0f2600ae-b3a2-11ef-8f0b-52540025e7a3] [error="workerpool: execute job no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed"] [stack="github.com/zilliztech/milvus-backup/core.(*BackupContext).RestoreBackup\n\t/home/runner/work/milvus-backup/milvus-backup/core/backup_impl_restore_backup.go:323\ngithub.com/zilliztech/milvus-backup/cmd.glob..func7\n\t/home/runner/work/milvus-backup/milvus-backup/cmd/restore.go:83\ngithub.com/spf13/cobra.(*Command).execute\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:876\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:990\ngithub.com/spf13/cobra.(*Command).Execute\n\t/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.5.0/command.go:918\ngithub.com/zilliztech/milvus-backup/cmd.Execute\n\t/home/runner/work/milvus-backup/milvus-backup/cmd/root.go:35\nmain.main\n\t/home/runner/work/milvus-backup/milvus-backup/main.go:24\nruntime.main\n\t/opt/hostedtoolcache/go/1.18.10/x64/src/runtime/proc.go:250"]
workerpool: execute job no binlog to import, input=[paths:"backup/mytest_bak_20241206/binlogs/delta_log/454414172884218510/454414172884218511/454414172884221072"]: importing data failed
duration:6 s

yhmo · 2024-12-06T08:09:12Z

yhmo
Dec 6, 2024
Collaborator

Maybe there are errors during the backup creation.
Normally, the backup folder should contain binlog folder.
I just created a backup to restore, everything works file.

3 replies

hxlsky Dec 6, 2024
Author

can you get me a example of the backup.yaml?

hxlsky Dec 6, 2024
Author

my milvus is deployed in k8s,not standalone.

hxlsky Dec 6, 2024
Author

my backup.yml just as flow show:

hxlsky · 2024-12-06T09:05:12Z

hxlsky
Dec 6, 2024
Author

this is check output:
[root@yunwei-k8s-dev conf]# /opt/milvus_backup/milvus-backup check --config=/opt/milvus_backup/conf/backup.yaml
0.4.19 (Built on 2024-08-14T07:14:01Z from Git SHA fb319d56c596114542d8319b8c4f690cf0867ad6)
config:/opt/milvus_backup/conf/backup.yaml
[2024/12/06 17:01:53.064 +08:00] [INFO] [logutil/logutil.go:165] ["Log directory"] [configDir=]
[2024/12/06 17:01:53.064 +08:00] [INFO] [logutil/logutil.go:166] ["Set log file to "] [path=logs/backup.log]
[2024/12/06 17:01:53.116 +08:00] [INFO] [storage/minio_chunk_manager.go:151] ["minio chunk manager init success."] [bucketname=a-bucket] [root=files]
Milvus storage is empty. Please verify whether your cluster is really empty. If not, the configs(minio address, port, bucket, rootPath) may be wrong
Milvus version: v2.4.15
Storage:
milvus-bucket: a-bucket
milvus-rootpath: files
backup-bucket: a-bucket
backup-rootpath: backup

2 replies

yhmo Dec 6, 2024
Collaborator

"Milvus storage is empty. ......" ---------------- This indicates the folder 192.168.1.246:9000//a-bucket/files is empty. Maybe your milvus is not using this path as its storage path.

hxlsky Dec 6, 2024
Author

there are no the files directory in minio

[root@ceph02 a-bucket]# pwd
/data/minio/data/a-bucket
[root@ceph02 a-bucket]# ls
[root@ceph02 a-bucket]#

hxlsky · 2024-12-06T09:20:10Z

hxlsky
Dec 6, 2024
Author

when i run the backup command(milvus-backup create),this is just only the meta directory

[root@ceph02 mytest_bak_20241206]# pwd
/data/minio/data/a-bucket/backup/mytest_bak_20241206
[root@ceph02 mytest_bak_20241206]# ls
meta

2 replies

yhmo Dec 6, 2024
Collaborator

All the collections in the mvsdb_ai are empty, right? So why do you want to backup empty collections?

hxlsky Dec 6, 2024
Author

the issue has sloved,it is mistaken by configure,thank you !

wxd1120 · 2024-12-17T08:10:43Z

wxd1120
Dec 17, 2024

I also encountered a similar problem when using backup. After the backup was completed, the target minio only had a meta directory and no binlogs directory. I confirmed that there was a files directory in the source minio and it was not empty. When backing up, I turned on the debug log. There was no error information in the log, and there was a log of successful data copying, but the data was not actually in the target minio.
Can anyone help me look at this problem?

[2024/12/17 15:42:32.339 +08:00] [DEBUG] [storage/copier.go:260] [copyRemote] [srcBucket=a-bucket] [destBucket=a-bucket] [key=files/insert_log/454216323608928169/454216323608928170/454216323608928261/102/454216323608928265] [destKey=backup/backup_test2/binlogs/insert_log/454216323608928169/454216323608928170/454216323608928261/454216323608928261/102/454216323608928265]
[2024/12/17 15:42:32.340 +08:00] [DEBUG] [core/backup_impl_create_backup.go:828] ["Successfully copy file"] [collection_id=454216323608928169] [partition_id=454216323608928170] [segment_id=454394814798303260]
[group_id=1] [from=files/insert_log/454216323608928169/454216323608928170/454394814798303260/102/454394814798303264] [to=backup/backup_test2/binlogs/insert_log/454216323608928169/454216323608928170/454394814798303260/454394814798303260/102/454394814798303264]
[2024/12/17 15:42:32.341 +08:00] [DEBUG] [storage/copier.go:260] [copyRemote] [srcBucket=a-bucket] [destBucket=a-bucket] [key=files/insert_log/454528208900921460/454528208900921461/454528208900928845/102/454528208900928849] [destKey=backup/backup_test2/binlogs/insert_log/454528208900921460/454528208900921461/454528208900928845/454528208900928845/102/454528208900928849]
[2024/12/17 15:42:32.341 +08:00] [DEBUG] [core/backup_impl_create_backup.go:828] ["Successfully copy file"] [collection_id=454216323608928169] [partition_id=454216323608928170] [segment_id=454216323608928261]
[group_id=1] [from=files/insert_log/454216323608928169/454216323608928170/454216323608928261/102/454216323608928265] [to=backup/backup_test2/binlogs/insert_log/454216323608928169/454216323608928170/454216323608928261/454216323608928261/102/454216323608928265]
[2024/12/17 15:42:32.342 +08:00] [INFO] [core/backup_impl_create_backup.go:615] ["Finish copy data"] [dbName=enos_knowledge] [collectionName=enos_knowledge_b6334dfeb72947b1a9746eaf99e10b68_chunks]
[2024/12/17 15:42:32.344 +08:00] [DEBUG] [core/backup_impl_create_backup.go:828] ["Successfully copy file"] [collection_id=454528208900921460] [partition_id=454528208900921461] [segment_id=454528208900928845]
[group_id=1] [from=files/insert_log/454528208900921460/454528208900921461/454528208900928845/102/454528208900928849] [to=backup/backup_test2/binlogs/insert_log/454528208900921460/454528208900921461/454528208900928845/454528208900928845/102/454528208900928849]

1 reply

yhmo Dec 17, 2024
Collaborator

The log shows the copy api of minio succeeded.
The backup.yaml defines the source and target:

minio:
  # Milvus storage configs, make them the same with milvus config
  storageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
  address: sourceAddress # Address of MinIO/S3
  port: 9000   # Port of MinIO/S3
  accessKeyID: minioadmin  # accessKeyID of MinIO/S3
  secretAccessKey: minioadmin # MinIO/S3 encryption string
  useSSL: false # Access to MinIO/S3 with SSL
  useIAM: false
  iamEndpoint: ""
  bucketName: "sourceBucketName" # Milvus Bucket name in MinIO/S3, make it the same as your milvus instance
  rootPath: "sourceRootPath" # Milvus storage root path in MinIO/S3, make it the same as your milvus instance

  # Backup storage configs, the storage you want to put the backup data
  backupStorageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
  backupAddress: backupAddress # Address of MinIO/S3
  backupPort: 9000   # Port of MinIO/S3
  backupAccessKeyID: minioadmin  # accessKeyID of MinIO/S3
  backupSecretAccessKey: minioadmin # MinIO/S3 encryption string
  backupBucketName: "backupBucketName" # Bucket name to store backup data. Backup data will store to backupBucketName/backupRootPath
  backupRootPath: "backupRootPath" # Rootpath to store backup data. Backup data will store to backupBucketName/backupRootPath

The file from:
sourceAddress/sourceBucketName/sourceRootPath/insert_log/454528208900921460/454528208900921461/454528208900928845/102/454528208900928849
is copied to:
backupAddress/backupBucketName/backupRootPath/backup_test2/binlogs/insert_log/454528208900921460/454528208900921461/454528208900928845/454528208900928845/102/454528208900928849

wxd1120 · 2024-12-17T09:57:34Z

wxd1120
Dec 17, 2024

我的minio源地址和目标地址配置如下，meta数据同步过去了，说明minio的连通性是没问题的
minio:
#Milvus storage configs, make them the same with milvus config
storageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
address: localhost # Address of MinIO/S3
port: 9000 # Port of MinIO/S3
accessKeyID: minioadmin # accessKeyID of MinIO/S3
secretAccessKey: minioadmin # MinIO/S3 encryption string
useSSL: false # Access to MinIO/S3 with SSL
useIAM: false
iamEndpoint: ""
bucketName: "a-bucket" # Milvus Bucket name in MinIO/S3, make it the same as your milvus instance
rootPath: "files" # Milvus storage root path in MinIO/S3, make it the same as your milvus instance

#Backup storage configs, the storage you want to put the backup data
backupStorageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
backupAddress: xx.xx.xx.xx # Address of MinIO/S3
backupPort: 9010 # Port of MinIO/S3
backupAccessKeyID: minioadmin # accessKeyID of MinIO/S3
backupSecretAccessKey: minioadmin # MinIO/S3 encryption string
backupBucketName: "a-bucket" # Bucket name to store backup data. Backup data will store to backupBucketName/backupRootPath
backupRootPath: "backup" # Rootpath to store backup data. Backup data will store to backupBucketName/backupRootPath

同时，在源minio里是有数据的

并且backup日志也显示已经从源地址成功拷贝到目标minio地址了，但目标地址的minio却根本没有binlogs这个路径

所以很疑惑中间哪里出了问题，或者是有什么配置没有配对？

1 reply

yhmo Dec 17, 2024
Collaborator

先看一下是不是上传到源minio的backup/backup4目录里了，如果是的话那就是bug了。
如果不是的话，把milvus-backup的完整日志发一下

hxlsky · 2024-12-18T01:03:17Z

hxlsky
Dec 18, 2024
Author

do you milvusdb in k8s or Standalone,if in k8s,you need to check the 2 items correctly.

3 replies

yhmo Dec 18, 2024
Collaborator

跟着以下步骤走一遍，以下步骤我验证是可以备份成功的：

用docker compose正常启动一个milvus standalone，其minio服务端口为9000/9001

version: '3.5'
services:
  etcd:
    container_name: milvus-etcd
    image: quay.io/coreos/etcd:v3.5.5
    ......
  standalone:
    container_name: milvus-standalone
    image: milvusdb/milvus:v2.5.0-beta
    ......
  minio:
    container_name: milvus-minio
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin
    ports:
      - "9001:9001"
      - "9000:9000"
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
    ......

用docker compose单独启动另一个minio服务，端口为29000/29001

version: '3.5'
services:
  minio:
    container_name: target-minio
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin
    ports:
      - "29001:9001"
      - "29000:9000"
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s
      retries: 3

浏览器登录localhost:29001，创建一个名为backup-bucket的bucket
修改milvus-backup tool的backup.yaml配置文件，指定源minio和目标minio

minio:
  # Milvus storage configs, make them the same with milvus config
  storageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
  address: localhost # Address of MinIO/S3
  port: 9000   # Port of MinIO/S3
  accessKeyID: minioadmin  # accessKeyID of MinIO/S3
  secretAccessKey: minioadmin # MinIO/S3 encryption string
  useSSL: false # Access to MinIO/S3 with SSL
  useIAM: false
  iamEndpoint: ""
  bucketName: "a-bucket" # Milvus Bucket name in MinIO/S3, make it the same as your milvus instance
  rootPath: "files" # Milvus storage root path in MinIO/S3, make it the same as your milvus instance

  # Backup storage configs, the storage you want to put the backup data
  backupStorageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
  backupAddress: localhost # Address of MinIO/S3
  backupPort: 29000   # Port of MinIO/S3
  backupAccessKeyID: minioadmin  # accessKeyID of MinIO/S3
  backupSecretAccessKey: minioadmin # MinIO/S3 encryption string
  backupBucketName: "backup-bucket" # Bucket name to store backup data. Backup data will store to backupBucketName/backupRootPath
  backupRootPath: "backup" # Rootpath to store backup data. Backup data will store to backupBucketName/backupRootPath

  # If you need to back up or restore data between two different storage systems, direct client-side copying is not supported. 
  # Set this option to true to enable data transfer through Milvus Backup.
  # Note: This option will be automatically set to true if `minio.storageType` and `minio.backupStorageType` differ.
  # However, if they are the same but belong to different services, you must manually set this option to `true`.
  crossStorage: "true"

crossStorage=true，因为是跨storage service备份
backupPort=29000
backupBucketName="backup-bucket"

用脚本建表，插入点数据

import random

from pymilvus import (
    connections,
    FieldSchema, CollectionSchema, DataType,
    Collection,
    utility,
)

connections.connect(host='localhost', port=19530)
print(utility.get_server_version())

collection_name = "AAA"
dim = 512

fields = [
    FieldSchema(name="id", dtype=DataType.INT64, is_primary=True, auto_id=False),
    FieldSchema(name="vector", dtype=DataType.FLOAT_VECTOR, dim=dim),
    FieldSchema(name="title", dtype=DataType.VARCHAR, max_length=100),
]
schema = CollectionSchema(fields)
utility.drop_collection(collection_name)

collection = Collection(collection_name, schema)
print(collection_name, "created")


count = 10000
data = [
    [k for k in range(count)],
    [[random.random() for _ in range(dim)] for _ in range(count)],
    [f"title_{k}" for k in range(count)],
]

collection.insert(data=data)
collection.flush()

这里调用了collection.flush()，以保证数据已落盘。实际上milvus-backup备份时也会执行一个flush操作

用milvus-backup 工具备份

./milvus-backup create -c AAA -n my_backup

AAA是表名，my_backup是备份名

浏览器登录localhost:29001，观察目录结构

my_backup目录下有binlogs和meta目录，binlogs下面有各个字段的数据文件

wxd1120 Dec 19, 2024

跟着以下步骤走一遍，以下步骤我验证是可以备份成功的：

用docker compose正常启动一个milvus standalone，其minio服务端口为9000/9001

version: '3.5'
services:
  etcd:
    container_name: milvus-etcd
    image: quay.io/coreos/etcd:v3.5.5
    ......
  standalone:
    container_name: milvus-standalone
    image: milvusdb/milvus:v2.5.0-beta
    ......
  minio:
    container_name: milvus-minio
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin
    ports:
      - "9001:9001"
      - "9000:9000"
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
    ......

用docker compose单独启动另一个minio服务，端口为29000/29001

version: '3.5'
services:
  minio:
    container_name: target-minio
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin
    ports:
      - "29001:9001"
      - "29000:9000"
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s
      retries: 3

浏览器登录localhost:29001，创建一个名为backup-bucket的bucket
修改milvus-backup tool的backup.yaml配置文件，指定源minio和目标minio

minio:
  # Milvus storage configs, make them the same with milvus config
  storageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
  address: localhost # Address of MinIO/S3
  port: 9000   # Port of MinIO/S3
  accessKeyID: minioadmin  # accessKeyID of MinIO/S3
  secretAccessKey: minioadmin # MinIO/S3 encryption string
  useSSL: false # Access to MinIO/S3 with SSL
  useIAM: false
  iamEndpoint: ""
  bucketName: "a-bucket" # Milvus Bucket name in MinIO/S3, make it the same as your milvus instance
  rootPath: "files" # Milvus storage root path in MinIO/S3, make it the same as your milvus instance

  # Backup storage configs, the storage you want to put the backup data
  backupStorageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
  backupAddress: localhost # Address of MinIO/S3
  backupPort: 29000   # Port of MinIO/S3
  backupAccessKeyID: minioadmin  # accessKeyID of MinIO/S3
  backupSecretAccessKey: minioadmin # MinIO/S3 encryption string
  backupBucketName: "backup-bucket" # Bucket name to store backup data. Backup data will store to backupBucketName/backupRootPath
  backupRootPath: "backup" # Rootpath to store backup data. Backup data will store to backupBucketName/backupRootPath

  # If you need to back up or restore data between two different storage systems, direct client-side copying is not supported. 
  # Set this option to true to enable data transfer through Milvus Backup.
  # Note: This option will be automatically set to true if `minio.storageType` and `minio.backupStorageType` differ.
  # However, if they are the same but belong to different services, you must manually set this option to `true`.
  crossStorage: "true"

crossStorage=true，因为是跨storage service备份 backupPort=29000 backupBucketName="backup-bucket"

用脚本建表，插入点数据

import random

from pymilvus import (
    connections,
    FieldSchema, CollectionSchema, DataType,
    Collection,
    utility,
)

connections.connect(host='localhost', port=19530)
print(utility.get_server_version())

collection_name = "AAA"
dim = 512

fields = [
    FieldSchema(name="id", dtype=DataType.INT64, is_primary=True, auto_id=False),
    FieldSchema(name="vector", dtype=DataType.FLOAT_VECTOR, dim=dim),
    FieldSchema(name="title", dtype=DataType.VARCHAR, max_length=100),
]
schema = CollectionSchema(fields)
utility.drop_collection(collection_name)

collection = Collection(collection_name, schema)
print(collection_name, "created")


count = 10000
data = [
    [k for k in range(count)],
    [[random.random() for _ in range(dim)] for _ in range(count)],
    [f"title_{k}" for k in range(count)],
]

collection.insert(data=data)
collection.flush()

这里调用了collection.flush()，以保证数据已落盘。实际上milvus-backup备份时也会执行一个flush操作

用milvus-backup 工具备份

./milvus-backup create -c AAA -n my_backup

AAA是表名，my_backup是备份名

浏览器登录localhost:29001，观察目录结构

my_backup目录下有binlogs和meta目录，binlogs下面有各个字段的数据文件

谢谢，是我配置的问题，我是从一台虚机迁移到另一台虚机的minio，crossStorage需要设置为"true"

wxd1120 Dec 19, 2024

do you milvusdb in k8s or Standalone,if in k8s,you need to check the 2 items correctly.

Thank you, I use standalone, it was my configuration problem. I migrated from one machine to another machine, and crossStorage needed to be set to "true"

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

why there is no the "binlogs" directory after milvus-backup #38279

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 6 comments 12 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

why there is no the "binlogs" directory after milvus-backup #38279

hxlsky Dec 6, 2024

Replies: 6 comments · 12 replies

yhmo Dec 6, 2024 Collaborator

hxlsky Dec 6, 2024 Author

hxlsky Dec 6, 2024 Author

hxlsky Dec 6, 2024 Author

hxlsky Dec 6, 2024 Author

yhmo Dec 6, 2024 Collaborator

hxlsky Dec 6, 2024 Author

hxlsky Dec 6, 2024 Author

yhmo Dec 6, 2024 Collaborator

hxlsky Dec 6, 2024 Author

wxd1120 Dec 17, 2024

yhmo Dec 17, 2024 Collaborator

wxd1120 Dec 17, 2024

yhmo Dec 17, 2024 Collaborator

hxlsky Dec 18, 2024 Author

yhmo Dec 18, 2024 Collaborator

wxd1120 Dec 19, 2024

wxd1120 Dec 19, 2024

hxlsky
Dec 6, 2024

Replies: 6 comments 12 replies

yhmo
Dec 6, 2024
Collaborator

hxlsky Dec 6, 2024
Author

hxlsky Dec 6, 2024
Author

hxlsky Dec 6, 2024
Author

hxlsky
Dec 6, 2024
Author

yhmo Dec 6, 2024
Collaborator

hxlsky Dec 6, 2024
Author

hxlsky
Dec 6, 2024
Author

yhmo Dec 6, 2024
Collaborator

hxlsky Dec 6, 2024
Author

wxd1120
Dec 17, 2024

yhmo Dec 17, 2024
Collaborator

wxd1120
Dec 17, 2024

yhmo Dec 17, 2024
Collaborator

hxlsky
Dec 18, 2024
Author

yhmo Dec 18, 2024
Collaborator