none
Network Out bandwidth with Azure File Share RRS feed

  • Question

  • Our multiple VMs have mount point for Azure File Share.

    Both VMs and Azure File share are in same region. But, when we copy data to Azure File Share, then it is considered as "Network Data out" of region. 

    The 'Network Data Out' metric continue to increment as we copy data. This affects our Azure bills significantly.

    Is this a bug or are we doing something wrong? We are facing this issue at multiple deployments.

    Monday, May 6, 2019 8:23 AM

All replies

  • As far as I know that the Network In/Out metric include the Performance Counter "Bytes Received/Bytes Sent". You will be charged only for the Network Out (Outbound Data). In Azure Outbound data transfer is charged at the normal rate and inbound data transfer is free.

    For example, if the file share and VM are in the same Azure region, there is no additional charge for the traffic between the file share and the VM. If the file share and the VM are in different regions, the traffic between them are charged as external bandwidth.

    If you have more questions/doubts I would suggest you to create a Free Billing support ticket.

    Kindly, let us know if you need any further assistance on this.

    Monday, May 6, 2019 12:51 PM
    Moderator
  • @TPS1511, Just checking in to see if the above answer helped. If this answers your query, do click “Mark as Answer” and Up-Vote for the same. And, if you have any further query do let us know.
    Thursday, May 9, 2019 5:15 AM
    Moderator

  • In my case, both file share and VM are in same Azure region. Azure file share is mounted on the VM. When user copies data from VM's disk to Azure File share using 'cp' command, then the Network Out metric shows data out.

    We have seen this behavior many times and always reproducible. 

    Following are the steps to reproduce the problem:

    1. Create Azure File Share 

    2. Create a VM in same region and same resource group

    3. Mount Azure File share on VM using method shown in Azure portal.

    4. Now, copy a big file from VM's filesystem to mount point of Azure file share.  You can use 'cp' command.

    5. Monitor the Network out metric. You will find it increases continuously. Also, it affects billing.

    We had filed a billing support ticket earlier. They acknowledged the issue but this is a problem for every billing cycle. Hence, product team should look into this to confirm if there is a bug in a system.

    Thursday, May 9, 2019 1:04 PM
  • Could you share the Azure support case number? We will look at the case details.


    Monday, May 13, 2019 5:25 AM
    Moderator
  • Some of the azure support cases: 118030717766646, 118040617950655

    It also very easy to reproduce the issue as per the steps mentioned in previous reply.

    Sunday, May 19, 2019 7:03 AM