Wasabi (S3) makes Veeam Console extremely slow

[unsichtbarre]

Happy Holidays!

I am testing Wasabi S3 on a very small testing) instance of VBR 11. The database is not large or old and the console was working great right up until the time I added Wasabi. My system shows very low CPU utilization and normal RAM utilization, yet the console has become nearly unusable.
My question is why?
I used the VBR server itself as Wasabi S3 gateway, created a local REPO, then Wasabi S3 Repo, then added local repo to SOBR as performance and Wasabi S3 as Capacity and then created a Backup Copy job targeting the SOBR.

Thanks!

[veremin]

We need to see the debug logs for this issue, so kindly collect those and attach to the support ticket. Once the case is opened, share its number here and we will follow the investigation internally.

Thanks!

[unsichtbarre]

Case #05205177

[veremin]

Thank you, John, for now let's wait and see what support engineer suggests after debug log review. We will chime in the investigation, should need be.

[jcavalear]

Was there any resolution to your case?

I am about to test this exact scenario. I have not created an jobs yet. I was wondering if there is a problem using this configuration?

VBR server itself as Wasabi S3 gateway, created a local REPO, then Wasabi S3 Repo, then added local repo to SOBR as performance and Wasabi S3 as Capacity and then created a Backup Copy job targeting the SOBR.

[veremin]

The ticket was closed due to no response. However, the configuration should not cause any issues. So feel free to deploy it. Thanks!