s3 Compatible location stopped working
Hello,
I have 9 servers that user S3 compatible backup to backup to Wasabi. As of yesterday, I have two servers that will no longer validate their S3 compatible destinations and backups have failed as a result.
1) If I look at the wasabi bucket can see files like validate.tmp-1703512-1669905287.txt in their backup folder in the bucket that correspond to the time validation was attempted. However, they fail validation.
2) I can ping the destination from terminal on each server that fails.
3) I tried to crate a new S3 compatible backup to backup to Wasabi on these two servers and those failed too.
4) the other 7 servers backup and validate to the same Wasabi bucket with same credentials without error.
Anyone else run into this?
To get backups backing up, I have created a temp destination to Back Blaze B2. That validated and works fine on these two servers.
Thanks,
Mike
-
check wasabi permissions. 0 -
Turned out Wasabi was having trouble on their end. As of 4:30PM CST they have addressed the issue and all is working again. 0 -
Glad to hear that the issue is solved :) 0 -
Hello! I'm glad to hear the issue is resolved, thank you for keeping us posted. 0
Please sign in to leave a comment.
Comments
4 comments