Hi Eric, Thanks a lot for replying,
> This line means that the upload was successful after 1 retry. The command AWS > had an error the first time and was OK the second time. That is what I initially assumed too, which is why I checked the bucket, and confirmed that part.2 was never uploaded to S3 at all when the job finished (unless this is caused by a misconfiguration in my setup). >From the SD log: 31-Oct 12:51 bacula-s3-01-vbdc-sd JobId 11: Bacula-client2-2093/part.1 state=done size=273 B duration=2s 31-Oct 12:51 bacula-s3-01-vbdc-sd JobId 11: Bacula-client2-2093/part.2 state=done retry=1/10 size=1.073 GB duration=14s msg= Child exited with code 1 Checking S3 right after the backup job completed shows part.2 is completely missing for volume 2093, while neighboring volumes have both parts: root@bck-bacula-s3-01:~# aws s3 ls bacula-s3-testing/Bacula-client2-2092/ 2026-10-31 11:58:13 273 part.1 2026-10-31 11:58:50 1073217525 part.2 root@bck-bacula-s3-01:~# aws s3 ls bacula-s3-testing/Bacula-client2-2093/ 2026-10-31 11:58:45 273 part.1 root@bck-bacula-s3-01:~# aws s3 ls bacula-s3-testing/Bacula-client2-2094/ 2026-10-31 11:59:18 273 part.1 2026-10-31 11:59:55 1073217533 part.2 At the same time, the local cache file remained in /backup/file01/Bacula-client2-2093/part.2, which means Truncate Cache = AfterUpload did not trigger because the upload never succeeded. Only after I manually ran cloud upload in bconsole did part.2 actually appear in S3 (along with an extra 0-byte timestamped object): * cloud upload pool=client2 storage=client2-stor volume=Bacula-client2-2093 Automatically selected Catalog: MyCatalog Using Catalog "MyCatalog" Connecting to Storage daemon client2-stor at bck-bacula-s3-01:9103 ... 3000 Cloud Upload: Bacula-client2-2093/part.2 state=done size=1.073 GB duration=10s The volume "Bacula-client2-2093" has been uploaded root@bck-bacula-s3-01:~# aws s3 ls bacula-s3-testing/Bacula-client2-2093/ 2026-10-31 11:58:45 273 part.1 2026-10-31 14:26:33 1073217536 part.2 2026-10-31 14:26:25 0 part20261031142624.2 I have enabled --debug logging on the aws CLI wrapper to investigate why the underlying aws command is failing on those 1-2% of uploads, but the fact that Bacula logs state=done with Child exited with code 1 and stops after retry=1/10 without uploading the object seems worth looking into as well. Best regards!
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
