milvus-backup(k8s)配置文件说明

 

复制代码
[root@yunwei-k8s-dev conf]# more backup.yaml 
# Configures the system log output.
log:
  level: info # Only supports debug, info, warn, error, panic, or fatal. Default 'info'.
  console: true # whether print log to console
  file:
    rootPath: "logs/backup.log"

http:
  simpleResponse: true

# milvus proxy address, compatible to milvus.yaml
milvus:
  address: 10.18.223.77
  port: 19530
  authorizationEnabled: true
  # tls mode values [0, 1, 2]
  # 0 is close, 1 is one-way authentication, 2 is two-way authentication.
  tlsMode: 0
  user: "root"
  password: "Milvus"

# Related configuration of minio, which is responsible for data persistence for Milvus.
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: 192.168.1.246 # Address of MinIO/S3
  port: 9000   # Port of MinIO/S3
  accessKeyID: root  # accessKeyID of MinIO/S3
  secretAccessKey: 123 # MinIO/S3 encryption string
  useSSL: false # Access to MinIO/S3 with SSL
  useIAM: false
  iamEndpoint: ""
  bucketName: "milvus-dev" # Milvus Bucket name in MinIO/S3, make it the same as your milvus instance
  rootPath: "milvus/milvus-dev" # 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: 192.168.1.246 # Address of MinIO/S3
  backupPort: 9000   # Port of MinIO/S3
  backupAccessKeyID: root  # accessKeyID of MinIO/S3
  backupSecretAccessKey: 123 # MinIO/S3 encryption string
  backupBucketName: "a-bucket" # Bucket name to store backup data. Backup data will store to backupBucketName/backup
RootPath
  backupRootPath: "backup" # Rootpath to store backup data. Backup data will store to backupBucketName/backupRootPat
h

  # 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: "false"
  
backup:
  maxSegmentGroupSize: 2G
  parallelism: 
    # collection level parallelism to backup
    backupCollection: 4
    # thread pool to copy data. reduce it if blocks your storage's network bandwidth
    copydata: 128
    # Collection level parallelism to restore
    restoreCollection: 2
  
  # keep temporary files during restore, only use to debug 
  keepTempFiles: false
  
  # Pause GC during backup through Milvus Http API. 
  gcPause:
    enable: true
    seconds: 7200
    address: http://10.18.223.77:9091
复制代码

 

  bucketName: "milvus-dev" #milvus使用的minio bucketname名称
  rootPath: "milvus/milvus-dev" # milvus使用的minio rootPath路径


  backupBucketName: "a-bucket" # 备份文件存放的bucketname名称
  backupRootPath: "backup" # 备份文件的目录


 

posted @   slnngk  阅读(45)  评论(0编辑  收藏  举报
相关博文:
阅读排行:
· DeepSeek 开源周回顾「GitHub 热点速览」
· 物流快递公司核心技术能力-地址解析分单基础技术分享
· .NET 10首个预览版发布:重大改进与新特性概览!
· AI与.NET技术实操系列(二):开始使用ML.NET
· 单线程的Redis速度为什么快?
历史上的今天:
2021-12-09 centos6安装部署ntp
2019-12-09 dataguard环境破坏后采用rman备份集重新部署
点击右上角即可分享
微信分享提示