milvus-backup.yaml 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107
  1. # Configures the system log output.
  2. log:
  3. level: info # Only supports debug, info, warn, error, panic, or fatal. Default 'info'.
  4. console: true # whether print log to console
  5. file:
  6. filename: "logs/backup.log"
  7. http:
  8. simpleResponse: true
  9. # Zilliz Cloud config.
  10. # If you want to migrate data to Zilliz Cloud, you need to configure the following parameters.
  11. # Otherwise, you can ignore it.
  12. cloud:
  13. address: https://api.cloud.zilliz.com
  14. apikey: <your-api-key>
  15. # milvus proxy address, compatible to milvus.yaml
  16. milvus:
  17. address: lq-milvus-release
  18. port: 19530
  19. user: "root"
  20. password: "Milvus"
  21. # tls mode values [0, 1, 2]
  22. # 0 is close, 1 is one-way authentication, 2 is mutual authentication
  23. tlsMode: 0
  24. # tls cert path for validate server, will be used when tlsMode is 1 or 2
  25. caCertPath: ""
  26. serverName: ""
  27. # mutual tls cert path, for server to validate client.
  28. # Will be used when tlsMode is 2
  29. # for backward compatibility, if not set, will use tlsmode 1.
  30. # WARN: in future version, if user set tlsmode 2, but not set mtlsCertPath, will cause error.
  31. mtlsCertPath: ""
  32. mtlsKeyPath: ""
  33. # Milvus replicate msg channel name, default is by-dev-replicate-msg
  34. rpcChannelName: "by-dev-replicate-msg"
  35. etcd:
  36. endpoints: 127.0.0.1:2379 # you can set multiple endpoints, separated by comma, for example: "127.0.0.1:2379,127.0.0.1:2380,127.0.0.1:2381"
  37. rootPath: "by-dev"
  38. # Related configuration of minio, which is responsible for data persistence for Milvus.
  39. minio:
  40. # Milvus storage configs, make them the same with milvus config
  41. storageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent), gcpnative
  42. # You can use "gcpnative" for the Google Cloud Platform provider. Uses service account credentials for authentication.
  43. address: lq-milvus-release-minio # Address of MinIO/S3
  44. port: 9000 # Port of MinIO/S3
  45. region: "" # region of MinIO/S3
  46. accessKeyID: minioadmin # accessKeyID of MinIO/S3
  47. secretAccessKey: minioadmin # MinIO/S3 encryption string
  48. token: "" # token of MinIO/S3
  49. gcpCredentialJSON: "/path/to/json-key-file" # The JSON content contains the gcs service account credentials.
  50. # Used only for the "gcpnative" cloud provider.
  51. useSSL: false # Access to MinIO/S3 with SSL
  52. useIAM: false
  53. iamEndpoint: ""
  54. bucketName: "milvus-bucket" #a-bucket Milvus Bucket name in MinIO/S3, make it the same as your milvus instance
  55. rootPath: "file" # Milvus storage root path in MinIO/S3, make it the same as your milvus instance
  56. # Backup storage configs, the storage you want to put the backup data
  57. backupStorageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)
  58. backupAddress: lq-milvus-release-minio # Address of MinIO/S3
  59. backupRegion: "" # region of MinIO/S3
  60. backupPort: 9000 # Port of MinIO/S3
  61. backupAccessKeyID: minioadmin # accessKeyID of MinIO/S3
  62. backupSecretAccessKey: minioadmin # MinIO/S3 encryption string
  63. backupToken: "" # token of MinIO/S3
  64. backupGcpCredentialJSON: "/path/to/json-key-file" # The JSON content contains the gcs service account credentials.
  65. # Used only for the "gcpnative" cloud provider.
  66. backupBucketName: "milvus-backup-bucket" # Bucket name to store backup data. Backup data will store to backupBucketName/backupRootPath
  67. backupRootPath: "backup" # Rootpath to store backup data. Backup data will store to backupBucketName/backupRootPath
  68. backupUseSSL: false # Access to MinIO/S3 with SSL
  69. # If you need to back up or restore data between two different storage systems, direct client-side copying is not supported.
  70. # Set this option to true to enable data transfer through Milvus Backup.
  71. # Note: This option will be automatically set to true if `minio.storageType` and `minio.backupStorageType` differ.
  72. # However, if they are the same but belong to different services, you must manually set this option to `true`.
  73. crossStorage: "false"
  74. backup:
  75. parallelism:
  76. # number of threads to copy data. reduce it if blocks your storage's network bandwidth
  77. copydata: 128
  78. # number of collections to backup in parallel.
  79. backupCollection: 4
  80. # number of segments to backup in parallel
  81. backupSegment: 1024
  82. # Collection level parallelism to restore
  83. restoreCollection: 2
  84. # max number of import job to run in parallel,
  85. # should be less than milvus's config dataCoord.import.maxImportJobNum
  86. importJob: 768
  87. # keep temporary files during restore, only use to debug
  88. keepTempFiles: false
  89. # Pause GC during backup through Milvus Http API.
  90. gcPause:
  91. enable: true
  92. address: lq-milvus-release