offloads to Backblaze from linux repo stopped working - stuck at Preparing Index

[gtelnet]

Anyone else see an issue where offloads to Backblaze s3 storage from linux repos stopped working in past few weeks? We're using Backblaze b2 storage and trying to offload directly from the linux server, without using a windows gateway. Conversely, is there anyone who's offloading directly from linux repos to Backblaze and is still working properly?

It was working fine for the past 6 months and then recently, all offload jobs started getting stuck at 'Preparing Index' and would stay at that step indefinitely. We've installed all of the v11 updates over the past several months, currently running the latest 525. Opened case # 04838936 and support had me try using a windows gateway for the offload, which works, but we're trying to limit the number of Windows servers we use for this environment and would really like to offload directly from the linux repos.

They first suspected firewall/connectivity rules, but we're able to browse the s3 bucket and all of it's contents from the linux repos using rclone and can get/put files in the bucket, so it doesn't seem to be a connectivity issue between linux and backblaze. Thank you in advance!

[veremin]

We will check the case internally and ask for additional assistance, if needed. Thanks!

[Ibeme]

Any news on this?

We are experiencing similar problems with a customer and our own offload to Wasabi since the beginning of the last week.

But we do only have Windows Gateways with the same problem.

Before it was also working fine.

[gtelnet]

Veeam support has had me do a bunch of testing from our linux repo and all tests were successful, but haven't made any progress on the offload, other than using the windows gateway. If yours isn't working at all, you should open a ticket, if you haven't already.

[Ibeme]

We already did that.
Currently it is unclear if it is related to Veeam or Wasabi.

[veremin]

We would appreciate, if you share the ticket Id with us, so we can check the current issue state. Thanks!

[bazedonia]

Hi there,
someone found a solution for this?
I have the same issue with Windows Gateway and MinIO.
Thanks!

[veremin]

In the OP's case the issue was caused by specific trunk aggregation settings.

If you experience the same problem, we recommend you opening a separate support ticket, as the causes might vary.

Thanks!

[gtelnet]

The fix in our case was a network related issue. We determined that one of the switch ports connected to the dual NICs on that linux repo was configured improperly, which caused offloads not to work when offloading directly from the linux repo, but would work fine when using a windows gateway. And just saw that veremin replied. Great case notes and quick reply!!