Issues connecting to Microsoft Azure appliance in Veeam Backup and Replication 11

[tobiejohnson.otr]

Hello all,

I have a support case open (opened over a month ago) Case # 04941275.

I have deployed an Azure Appliance through the marketplace, can hit the web portal, and successfully run backups/restore operations. The compute account has complete access to the subscription, and I am able to connect to blob storage using a storage account on the same B&R server. In backup infrastructure, I right-click Managed Servers, then select Add server. In the Add Server wizard, I select Veeam Backup for Microsoft Azure, connect to an existing appliance, select my Microsoft Azure compute account, then click next. I get the following error:

"Failed to create connection. The SSL connection could not be established, see inner exception."

The ticket has been escalated to a tier two tech that has been trying to recreate the issue in their lab. It has been 32 days since the initial request was put in, and it has not progressed at all. I was hoping someone here has encountered the same issue?

[veremin]

It seems that T2 support engineer is still in contact with you - he responded today and was about to ask for assistance from T3 engineer. The case is being actively handled, so let's just wait and see what engineers find. Thanks!

[tobiejohnson.otr]

I am aware the T2 support engineer replied today (his reply is that after the past 7 days of troubleshooting he has not been able to replicate my issue), my concern is the amount of time it has taken (with 0 progress) since the request was opened initially, and that it is just now being escalated. We need this functionality to work for production server backups, and I do believe it does not hurt anyone to ask for the community's input if they've seen the issue before.

To be clear, I've only ever had great support and customer service from Veeam. I 100% drink the Veeam juice and fight to use it anywhere my career brings me. It just seems in this specific case, it is not being escalated properly. Still 100% a Veeam fanboy though

[veremin]

We cannot comment on the speed of the investigation process, but based on the correspondence history the case seems to be handled carefully - it might just happen that the specific problem requires more time to find the root cause and the fact that the issue has not been reported before just confirms this assumption.

So for now the best strategy will be to wait, until Tier 3 engineer analyzes the ticket and comes up with the conclussion.

Thanks!

[tobiejohnson.otr]

I agree to a certain degree, but I don't quite understand the logic behind telling someone to stop asking other users of your product if they've experienced the same or similar issues. Just because an issue has not been reported (or does not exist in your knowledge base) does not mean it is the first time it has occurred. Once this issue is fixed, the solution could be posted here for others to reference in the future as well. Surely you agree with that!

[veremin]

Sure, I agree and haven't tried to question that or steered the discussion away from the forums - I was just clarifying the situation with the support case and proposing the best strategy (at least from my perspective)

[tobiejohnson.otr]

Just wanted to dump the conclusion of this ticket here. The ticket was open for a grand total of 6 months and 10 days, ticket # for reference is #04941275.

The issue was caused by disabling a required cipher required by Veeam to operate. Don't use IIS Crypto best practices and this won't happen to you.

Code: Select all

443/tcp open https
| ssl-enum-ciphers:
| TLSv1.2:
| ciphers:
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256 (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
| TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 2048) - A
| TLS_RSA_WITH_AES_256_CCM_8 (rsa 2048) - A
| TLS_RSA_WITH_AES_256_CCM (rsa 2048) - A
| TLS_RSA_WITH_ARIA_256_GCM_SHA384 (rsa 2048) - A
| TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_128_CCM_8 (rsa 2048) - A
| TLS_RSA_WITH_AES_128_CCM (rsa 2048) - A
| TLS_RSA_WITH_ARIA_128_GCM_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
| TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (rsa 2048) - A
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
| TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (rsa 2048) - A