I'm trying to configure NB 8.0 with HCP 7.3.3 and constantly getting following error in NB tpcommand log
cURL error: 51 (SSL peer certificate or SSH remote key was not OK). Any ideas?? thanx
Solved. Misconfiguration of namespace sizes. thank you
I'm assuming you are using the Cloud Connector, or the Cloud Catalyst connector to connect to HCP via HS3?
If so, you need to have HS3 protocol configured on the namespace.
Also the username & password have to be base64 and md5 encoded respectively. (you do not use the actually username and password with S3, you use the hash's of them)
You can use this website to output the appropriate hash HCP S3 User/Password Hash
Hope that helps!
I'm trying to configure Netbackup 8.0 to connect to HCP via HS3. HS3 access keys and secret are ok. Used HCP tool to convert username and pass. Completely differnet error if user & pass are wrong. Now I'm getting following error
HTTP code 400, server error code MalformedXML, Authorization information parse exception: Unknown signature version
Still getting cURL error: 51 (SSL peer certificate or SSH remote key was not OK).
Have found that using cURL directly can be useful to diagnose connectivity / set up issues with HS3 protocol. Need to see exactly what it is complaining about rather than the top level message at NBU. Could be the URL for the tenant, the lack of a valid cert on HCP (the one it comes with is self signed), the credentials, soemthing else... If you try cURL from the command line you might get some insight. Have not tried NBU with HCP yet but want to, so good luck and keep us posted!
Solved problem with cURL. By default HCP uses selfsigned cert. Now I'm stuck with adding disk volume to disk pool.
any suggestions. thanx
Retrieving data ...