I am using bacula v9.4.4 community edition on CentOS 7 server.
I am trying to use minio to send backup to backblaze storage.
From the logs it looks like quite a few hiccups occur with messages
similar to this:
msg=S3_put_object ERR=ConnectionFailed
At the very end of the backup log file there is a message like this:
Termination: Backup OK -- Upload to Cloud failed
When looking at the smaller "part" files that make up a volume on the
backblaze server, the parts that had errors in the log message appear to
have 2 revisions of the file and the total file size of that part to be
roughly double of the designated size of the part. I assume this not to
be horribly abnormal as I assume the part is uploaded twice. Although
the bacula log file does not really say that the volume was re-uploaded,
I am just guessing that is what happens.
Anyway, to be safe, I thought it might make sense to use the "cloud"
functions from bconsole to sync the volume to the cloud. When I choose
the "cloud" option and choose the appropriate storage, pool, and volume,
it looks like the upload is unsuccessful and the following error is
given:
3999 Error with the upload: ERR=SignatureDoesNotMatch
As far as I can tell, that may be a minio/aws error, and I can't find
anything necessarily related to bacula with the error.
Is anyone here familiar with this error, and know the resolution?
Thank You.
-Scott
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
