We just switched from AWS to Wasabi and it's a mess. Not only offloads are taking much longer and failing, even backup jobs take >24h. The backup itself is done pretty quick to performance tier but then the retention/cleanup takes ages. TCP connection limit on Wasabi side was already removed. I'm currently spending hours in calls and on cases with Veeam support to clean up the mess. The latest changes to offloading in Veeam also added new issues. I think we have now the 3rd hotfix for latest versions with more to come. Even reducing concurrent tasks to 8 did not solve the issues. The opposite, we learned the hard way that offloading breaks in cases where too many tasks are fighting for slots (result: endless loop).Hi -
We're looking at possibly using Wasabi for offsite storage. We're comparing Azure, AWS, and Wasabi. I would be interested in any real world issues anyone can share with these 3 services? I had an Veeam support person who expressed that Wasabi does have some issues with Veeam and I believe Veeam prefers to use S3.
Any info would be appreciated.
Thanks.
Lewis
Wasabi promised that the situation will change as they have changed something in the background. We will see.
But it's also Veeam offloading that is still kind of experimental. We use this now for 4 years and I still spent a lot time reporting issues/bugs.
Statistics: Posted by pirx — Apr 20, 2024 7:46 am
