attu b6 backup s3 failed #1013

Activity

1. shanghaikid commented on Jun 10, 2026

   

   shanghaikid

   on Jun 10, 2026

   Collaborator

   More actions

   Thanks for reporting this.

   We tested the AWS S3 backup path with milvus-backup 0.5.16 and confirmed that S3 can work as the backup target through the full flow: check, create, list, restore, and delete.

   This specific error does not look like an AWS S3 connectivity or permission failure:

   segment 464629288825733969 has no insert logs
   

   At this point the backup task has already passed the storage connection/authentication stage and is copying collection segment data. The error means Milvus returned segment 464629288825733969, but that segment did not have insert logs for milvus-backup to copy.

   This usually points to the source collection or segment state, for example:

   • the collection was being written/imported/compacted during backup
   • data had not fully flushed or settled yet
   • the segment metadata exists, but its binlog/insert log metadata is empty or inconsistent

   Please try:

   1. Stop writes/imports/compaction for this collection.
   2. Flush the collection.
   3. Wait for the segment state to settle.
   4. Retry the backup.

   If it still fails, please share DataCoord logs around segment 464629288825733969 and the segment/collection state.

   We also agree the current Attu UI message is too raw here. We are improving the error classification so this will be shown as a source collection/segment data issue instead of the long UNKNOWN: backup: ... chain.
2. cnangel commented on Jun 11, 2026

   

   cnangel

   on Jun 11, 2026

   Author

   More actions

   We cannot stop the write operation, and there are no import/compression tasks.
   I tried flushing the collection, but it didn't work. Retrying also had no effect.
   milvus-backup issue? Could you give them some feedback?
3. shanghaikid commented on Jun 11, 2026

   

   shanghaikid

   on Jun 11, 2026

   Collaborator

   More actions

   can you run deep check, and show me the result ? thanks

   
4. cnangel commented on Jun 11, 2026

   

   cnangel

   on Jun 11, 2026

   Author

   More actions

   
5. cnangel commented on Jun 11, 2026

   

   cnangel

   on Jun 11, 2026

   Author

   More actions

   I think it's a timeout issue?
6. cnangel commented on Jun 11, 2026

   

   cnangel

   on Jun 11, 2026

   Author

   More actions

   

   The other S3 had the same problem.
7. cnangel commented on Jun 11, 2026

   

   cnangel

   on Jun 11, 2026

   Author

   More actions

   

   Sometimes it crashes