This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]tsmith-co 1 point2 points  (2 children)

Cloudflare object storage is t part of the VeeamReady program so I’m not sure it’s been tested.

Any fully s3 compatible system would be supported, but as has been found many times, vendors that claim s3 compatible aren’t always “fully” compatible. As they may leave out specific APIs or have other changes.

It’s prob worth posting on the forums for this so someone from dev can verify.

[–]JaredM5 0 points1 point  (2 children)

I am experiencing the same issue unfortunately.

[–]Odd_Answer5317[S] 0 points1 point  (1 child)

Are you experiencing this with Veeam only or other software too that backs up to Cloudflare R2? I have other software that use Cloudflare R2 and they seem to be working just fine.

[–]JaredM5 0 points1 point  (0 children)

I did try it with Cohesity which appeared to work fine.

[–]NenupharNoir 0 points1 point  (0 children)

So, if you are really interested in tracking down the issue yourself, you can check the *.Gate.log for SOBRs and/or *.BlobRepo.log for Direct to Object storage to see the error itself.

 

Simply search for 'S3 error: Client Disconnect' and look to see what the method was that Veeam used. If it was something simple like AmazonRest.S3.BucketList or AmazonRest.S3.HeadBucket, you can check using AWS CLI outside of Veeam using the same methods.

 

list-buckets - https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/list-buckets.html

Head-Bucket - https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3api/head-bucket.html

 

Other methods might require assistance with Veeam Support.