Hello @radi 

Can you advise the type of backup and Commvault version?

I’m looking at some other cases that report this error they mostly have been addressed by the customer and closed off without an answer as to what the issue was.

Can you perform a cloud test tool onto the library:

https://documentation.commvault.com/v11/expert/testing_connectivity_with_cloud_test_tool.html

You can also test a number of the functions with this tool: 

https://documentation.commvault.com/v11/expert/performing_functionality_checks.html

Kind regards

Albert Williams

Hi @Albert Williams 

full backup and differential backup types, version 11.28.true, I have tried reading several other cases closed with no answer

Thanks

Regards

Radi

Hello @radi 

Is the cloud library showing online in Commvault? Can you check cloudactivity.log to see any curl errors show up related to cloud? 

Best,

Rajiv Singal

Hi @Rajiv 

yes, I checked cloudactivity.log, there are some curl errors showing up, 

pcvd] CURL error, CURLcode= 28, Timeout was reached
/cvd] Curl Error: 28
/cvd] retryable error

pEvMgrs] CURL error, CURLcode= 60, SSL peer certificate or SSH remote key was not OK
/EvMgrs] Curl Error: 60, GET https://xxxxxx
/EvMgrs] CURL error, CURLcode= 60, SSL peer certificate or SSH remote key was not OK
/EvMgrs] Curl Error: 60, GET https://xxxxxxx
/EvMgrs] CURL error, CURLcode= 60, SSL peer certificate or SSH remote key was not OK
/EvMgrs] Curl Error: 60, GET https://xxxxx

Thanks 

Regards 

Radi

Hello @radi is the cloud library showing online with which the MA is associated? Can you try to add the below additional key on the MA and restart the MA services and then check?

https://documentation.commvault.com/additionalsetting/details?name=%22nCloudServerCertificateNameCheck%22&id=4571

Name - nCloudServerCertificateNameCheck
Category - MediaAgent
Type - Integer
Value - 0

Best,

Rajiv Singal

I know this is old, but hopefully may help someone if they run into the same error. I confirmed that in the cloud logs i did see 403 errors. 
After logging into our buckets using s3 browser with the same credentials as what was in the storage library, i confirmed it was a change in how the info was entered with the service host in the mount paths to the buckets.

We had previously had xxxx.xxx.domain:443 for the service host, which worked fine for years. After our media agents had their software cache updated, this would throw errors. The fix was to remove the port info in the buckets to just show xxx.xxx.domain.