question

AnandFranklin-3216 avatar image
0 Votes"
AnandFranklin-3216 asked SadiqhAhmed-MSFT answered

STORAGE_COMMUNICATION_ERROR. Unable to communicate to Azure Storage blob.

Hello,

I have ran the ASR Deployment Planner tool, and provided the storage account name and key, but the tool does not calculate the bandwidth throughput information, and I get the below errror.

I have more than 100mbps of internet speed. Should the Hyper-V Host authentication credentials should have access to the storage account as well?.

Please assist. Anand




HYPER-V TO AZURE ASR DEPLOYMENT PLANNER

Finding achievable throughput from server 'NJPNXTFMSVR' to Azure storage account 'crmdrstorage'. It might take from few minutes to hours based upon bandwidth availability and number of VMs in the given filename. Please wait...
Creating VHDs
Uploading VHD files to storage account: crmdrstorage...
Error in uploading files. Failed to calculate achievable throughput.
Possible reasons:
1. STORAGE_COMMUNICATION_ERROR. Unable to communicate to Azure Storage blob. Check network connectivity to Azure and if bandwidth from on-premises to Azure is very low.
Deleting 'asrvhdfile*' files from storage account...
Successfully deleted files.
Deleting 'asrvhdfile*' files from local machine...
Successfully deleted the files.
Get throughput operation failed.

azure-site-recovery
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SadiqhAhmed-MSFT avatar image
0 Votes"
SadiqhAhmed-MSFT answered

Hello @AnandFranklin-3216 Sorry for the inconvenience caused!

This could be caused by the upload of a large file in a very low bandwidth availability, in this case we encourage implementing a retry-policy for blob Service, this post might be of help: https://github.com/Azure/azure-storage-node/issues/297

 var retryPolicy = new AzureStorage.ExponentialRetryPolicyFilter();
 var blobService = AzureStorage.createBlobServiceWithSas(…).withFilter(retryPolicy);

Also have you used this specific tutorial in the above scenario to make sure that you have enough bandwidth? https://docs.microsoft.com/en-us/azure/site-recovery/hyper-v-deployment-planner-overview

It could be that there are throttling rules in the internal network which maybe causing issues as well.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.