milvus-backup icon indicating copy to clipboard operation
milvus-backup copied to clipboard

[Bug]: errors of "no such file or directory" were thrown when perform backups with local storage

Open jason-ltc opened this issue 7 months ago • 1 comments

Current Behavior

When I perform backups with Milvus server running with local storage not MinIO/S3, errors of "no such file or directory" were thrown and the backups aborted:

...
[2024/07/24 14:59:28.248 +00:00] [INFO] [core/backup_impl_create_backup.go:774] ["Fail to copy file after retry"] [collection_id=451006378475358804] [partition_id=451006378475358805] [segment_id=451006378475358867] [group_id=1] [error="All attempts results:\nattempt #1:open /var/lib/milvus/backup/milvus_dump_202407241459/binlogs/delta_log/451006378475358804/451006378475358805/451006378475358867/451006378475358867/451125850870908498: no such file or directory\nattempt #2:open /var/lib/milvus/backup/milvus_dump_202407241459/binlogs/delta_log/451006378475358804/451006378475358805/451006378475358867/451006378475358867/451125850870908498: no such file or directory\nattempt #3:open /var/lib/milvus/backup/milvus_dump_202407241459/binlogs/delta_log/451006378475358804/451006378475358805/451006378475358867/451006378475358867/451125850870908498: no such file or directory\nattempt #4:open /var/lib/milvus/backup/milvus_dump_202407241459/binlogs/delta_log/451006378475358804/451006378475358805/451006378475358867/451006378475358867/451125850870908498: no such file or directory\nattempt #5:open /var/lib/milvus/backup/milvus_dump_202407241459/binlogs/delta_log/451006378475358804/451006378475358805/451006378475358867/451006378475358867/451125850870908498: no such file or directory\nattempt #6:context canceled\n"] [from=/var/lib/milvus/data/delta_log/451006378475358804/451006378475358805/451006378475358867/451125850870908498] [to=/var/lib/milvus/backup/milvus_dump_202407241459/binlogs/delta_log/451006378475358804/451006378475358805/451006378475358867/451006378475358867/451125850870908498]
...

backup.log

I checked both source and dest in the above error message:

  • the from path exists, and it's a file
  • the to path does not exist, as well as its parent dir
  • furthermore, the top dir BACKUP_DIR/binlogs/delta_log was not created the whole time

Expected Behavior

Both insert and delta binlogs should be copied to the backup destination.

Steps To Reproduce

- A Milvus 2.4.x standalone server uses local storage not MinIO, running with some insert and delta logs
- Use Milvus Backup 0.4.17 to do local backups

Environment

No response

Anything else?

No response

jason-ltc avatar Jul 24 '24 18:07 jason-ltc