01-30-2019 01:44 AM
Has anyone used a Azure Germany Cloud Storage successfully and could provide some simple steps howto create a *working Storage account* ?
I tried all type of storage accoungs (V2, Blob, Classic).
I used the storage account name and key1 or key2.
I created a firewall rule to allow all traffic fro backup server to internet with no interference of firewall or traffic inspection.
BE 20.2 will not connect to azure germany.
Thanks
Jürgen
Solved! Go to Solution.
01-30-2019 11:00 PM
choose blob storage while creating the storage account and choose access tier as cool or hot. The account that will be used in BE should have the storageaccount name as the username and password can be key1 or 2. Azure germany is supported in BE since version 16 FP2.
https://download.veritas.com/resources/content/live/OSVC/100041000/100041309/en_US/be_20_hcl.html?__...
Please debug the issue with sgmon and attach the log.
Launch SGMON.exe from BE Install Path
From under debug tab -> capture -> select beserver, bengine, device and media (additionally choose verbose from settings -> device and media -> click Ok ). Ensure captue to file checkbox is selected as well.
Configure cloud storage. When the error appears on UI, go to BE Install path\Logs. Copy and attach the ServerHostname-SGMON.log
Note : https://www.veritas.com/support/en_US/article.100044307
https://www.veritas.com/support/en_US/article.100032993 (Its a netbackup document but if the error matches the same steps can be followed. The cacert.pem file is present in BE Install Path in BE)
01-30-2019 11:00 PM
choose blob storage while creating the storage account and choose access tier as cool or hot. The account that will be used in BE should have the storageaccount name as the username and password can be key1 or 2. Azure germany is supported in BE since version 16 FP2.
https://download.veritas.com/resources/content/live/OSVC/100041000/100041309/en_US/be_20_hcl.html?__...
Please debug the issue with sgmon and attach the log.
Launch SGMON.exe from BE Install Path
From under debug tab -> capture -> select beserver, bengine, device and media (additionally choose verbose from settings -> device and media -> click Ok ). Ensure captue to file checkbox is selected as well.
Configure cloud storage. When the error appears on UI, go to BE Install path\Logs. Copy and attach the ServerHostname-SGMON.log
Note : https://www.veritas.com/support/en_US/article.100044307
https://www.veritas.com/support/en_US/article.100032993 (Its a netbackup document but if the error matches the same steps can be followed. The cacert.pem file is present in BE Install Path in BE)
01-31-2019 12:56 AM
Thanks Gurvinder,
this was really a good help to get a bit closer to the problem.
Why does Veritas support can´t come up with such a good troubleshooting?
The Problem is not still solved, but i think ...
Veritas hasn´t done Quality right, the application doesn´t trust the certificate from D-Trust GmbH here in Germany.
'Azure: CAzureErrorHandler::~CAzureErrorHandler:<RETRY HISTORY> Retry#:[1] , Request Type = GET, Request URI = https://veritasbackupcl01.blob.core.cloudapi.de/?comp=list&maxresults=1, Error code string:[No error code string available]'
'Azure: CAzureErrorHandler::~CAzureErrorHandler: Printing history:<RETRY HISTORY> cURL error: 60(Peer certificate cannot be authenticated with given CA certificates), multi cURL error: 0(OK),
So my next steps would be to check if i can add the certifiacte as described here
https://www.veritas.com/support/en_US/article.100032993
Thanks
Jürgen
01-31-2019 01:13 AM
you can append the cert to cacet.pem and that should solve it.
01-31-2019 01:15 AM - edited 01-31-2019 01:19 AM
Thanks,
i added both root ca and sub-ca to the cacert.pem and after a few second i see the azure cloud storage and the blob i created.
But this shows, that Veritas hasn´t tested against Azure Germany.
Moderately qualitity
Thanks for the help