Unable to Connect Backup Exec 16 to Azure Cloud Storage

[ocnalops]

Hi to All,

Have been Fighting for 2 days now trying to connect backup exec 16 to Azure Cloud Storage am using windows 2008 server R2 with backup Exec 16 And Symantec Endpoint protection 12.1 MP6, have read all about the way to do it correctley that exists on the internet, am connecting to server Azure:azure.com, have made sure that outgoing ports 80 and 443 are allowing trafic correctley have made sure that both outgoing and incoming port 10000 is open, and every time I try to connect the connector keeps throwing back BEMSDK Failure code A0009B23 it seems to do this without even trying to connect as the error is immediate any great ideas would be great a thousand thanks in advance to all.

[CraigV]

In this case it's probably best to log a call directly with Veritas to get this resolved. Once done, post back here with the solution. Thanks!

[ocnalops]

Sorry forgot to say am trying out Trial Version of backup Exec 16 so I believe that tecnical assistance from veritas directley is not possible which is why am Posting to this foro, anyone any ideas based on problems with earlier version of backup exec.....???

[ocnalops]

Just to confirm suspicions if anyone had any doubt on the matter please find transcription of the chat just held with veritas tecnical Dept.

:I am sorry,but we cannot create the case with the technical team for trial version you need to have active maintenance for it.

However you can to to the veritas foram.

As always Veritas making friends and trying to sell a product before it works corectley.

[Colin_Weaver]

A0009B23 is a generci code taht is returne when we canot connect to the S3 service.

Typically this is one of teh following:

Invalid Bucket configuration (inside your S3 cloud setup)

Invalid credentials entered into Backup Exec for connecting to the cloud

Invalid name resolution against the cloud services being configured

Lack of access across the internet to the cloud provider from your Backup Exec server

You can check some of the above by using a 3rd party tool such as the free S3browser from

http://s3browser.com/

This would need to be downloaded and run on the BE server itself.

 Launch the S3 browser and add an S3 account. Use the information to connect to the bucket. Does it work? Can you get into the bucket? If you can…can you copy a file to the bucket, etc.

Note: as this is 3rd party software - this advice is on a use at your own risk basis.

[ocnalops]

Hi Colin first off a thousand thanks for the help, just one thing am trying to connect to Microsoft azure not S3, Will this third party tool also work with azure...???

[Colin_Weaver]

If azure use S3 protocols then yes it it does not then no - the reason I posted the S3 stuff is that the error code you provided is definitely one seen when trying to setup S3 (however is is possible then that same code is seen for all cloud setups and not just S3)

[Colin_Weaver]

It might be worth watching this video as it may show if you have missed an important step

https://www.youtube.com/watch?v=yF04UPLw3zg

[Shawn_Lemay]

That video really does show almost everything - few minor things to setup in Azure (storage itself, container too) - but those are fairly straight forward.

[Graham_Hodgetts]

Hi,

Was this ever resolved? I have the same issue here.

However, the error only occurs with a named proxy. If you use a direct connection, your don't receive the error.

Thanks

[Gurvinder]

This article is for Netbackup but if the error in the SGMON debug is the same, it would apply. You can launch SGMON.exe from BE Install Path -> select bengine, device and media and beserver. Then configure azure cloud storage. If a failure is seen then review the sgmon log for following error :

cURL error: 60(Peer certificate cannot be authenticated with given CA certificates)

https://www.veritas.com/support/en_US/article.1000329933

Also make sure BE 16 is patched with latest Feature Pack 2

You can also try connecting to Azure cloud storage container using Azure storage explorer to verify it is accessible.