Hello Martin,
Glad to hear that!
Thanks a lot for the feedback. :-)
You are very welcome!
Best regards,
Ana
On Fri, Jun 14, 2024 at 10:26 AM Martin Reissner
wrote:
> Hello Ana,
>
> I wanted to report back that after almost two weeks on Bacula 15.0.2 using
> the "Amazon" driver, the situation
Hello Ana,
I wanted to report back that after almost two weeks on Bacula 15.0.2 using the
"Amazon" driver, the situation has improved a lot. We have seen no more backups
failing because of timeouts. I had some errors with Copyjobs that are
reading from S3/RGW and writing to file storage but
Hello Martin,
Yes, the Amazon driver will help with the timeout issues. And we have been
improving the Amazon driver continuously. Thus, I would move to this one.
If you still see this issue related to the volume not marked as error, then
we should investigate it.
Best,
Ana
On Wed, May 15, 2024
Hello Ana,
thank you for the heads up. An upgrade to one of the more recent versions has
been in my backlog for a while now, maybe this will get me some time to
actually get it done.
I'd still like to know whether what I am seeing with the volume not being marked Error is
an actual bug or
Hello Martin,
Do you think you can upgrade to 15.0.X? I would recommend you to use the
"Amazon" driver, instead of the "S3" driver. You can simply change the
"Driver" in the cloud resource, and restart the SD. I'm not sure the Amazon
driver is available in 13.0.2, but you can have a try.
The
Hello,
by now I am mostly using our Ceph RGW with the S3 driver as storage and this
works just fine but time and again requests towards the RGW time out.
This is of course our business and not Bacula's but due to a behaviour I can't
understand this causes us more trouble than it should.
When
