S3 Compatible - Cohesity

[chris.childerhose]

We have set up our Cohesity unit with the S3 ability, but when trying to add an S3 Compatible repository, I get an error about the Region and Credentials. It also references the XML file in the program folder where I saw that you could set up a custom S3 repository, so I did but still have issues.

Does anyone have suggestions? I have opened a case with Veeam on this too - # 03909986

[Mike Resseler]

Chris,

Cohesity is not on our S3 storage compatibility list I'm afraid. And to be honest, I have no idea how their implementation of S3 is.
The only thing that I can think off (if it would be compatible) is that you are adding non-https?

[chris.childerhose]

Hi Mike,

Seems that the SSL is expired so we are going to fix that and try again. It is being added with HTTPS not HTTP. I will update again once this is done.

[Refruit]

Hello,

we wanna do the same and we're getting the same XML (3,3) error when trying to add cohesity as a s3 compatible storage repository to our VBO 365 v4 Server.
The Cohesity certificate is valid and we can see with wireshark, that we are passing the SSL handshake successfully.
We can browse the cohesity s3 buckets on this explicit server with a s3 browser like Cyberduck or using AWS CLI so there aren't any firewall/network restrictions.

The interesting thing with that is that we also have a VBR 9.5 U4 in production and on this side, we can add the same cohesity storage as s3 compatible storage repository without any problems using the same preferences like on the VBO Server.

Case Number is the following #04030309

Any suggestions why this behavior occurs?

[nielsengelen]

Best is to work via support as the XML error most likely requires a hotfix (from the looks of it).

[chris.childerhose]

@Refruit -- If you get a hotfix let me know as I can contact Support for this. The problem we seemed to have was the SSL certificate was a self-signed one which seemed to be the issue. We did not replace it as we moved away from testing but I may do that in the future.

[Refruit]

@chris.childerhose -- the problem should not be the certificate, because we're passing the SSL handshake and there is a short data exchange afterwards (Listing all buckets -> those are shown on VBR side) but maybe the XML response/format (XML validator sais everything is fine) or whatever is wrong for vbo 365

[chris.childerhose]

Gotcha. Hmm so maybe we need the hotfix then once it is created. I will monitor this forum post once you find out from Support with your case.

[Refruit]

Finally, today after more than 2 months we managed to backup data with VBO365 to cohesity as s3 compatible storage.
It was needed to apply hotfixes on veeam and cohesity side to get this working (for the moment only in a test environment)

The cohesity patch was applied for cluster version 6.4.1a but i already asked when this patch will be included in a LTS version (maybe 6.3.1f?)
On VBO365 side we are currently using build 4.0.0.1607 which might be unofficial at the moment.

[nielsengelen]

Thanks for the update Refruit. That looks like an unofficial build number due to the applied hotfixes. It is good information to know for the future.