Q: If I use server-side copy capabilities in Azure to copy data between storage accounts, do I pay for any network traffic?
A: If you need to move data between storage accounts in Azure that are in different regions, instead of downloading the data to your location and then uploading back into Azure, you can use a server-side asynchronous copy that leverages the Azure network backbone to perform the actual copy and avoid the data ever leaving Azure. If this copy is between storage accounts in different regions, then you will be responsible for the network egress costs because for most Azure traffic you pay for traffic outbound from an Azure data center (even if it's going to another Azure data center).
There are many ways to leverage the server-side copy; some good examples include:
- The Start-CopyAzureStorageBlob cmdlet, which performs an asynchronous, server-side copy of blobs between storage accounts.
- AzCopy, which enables the uploading, downloading, and copying of data related to Azure.
- Third-party graphical tools, such as ClumsyLeaf Software's CloudXplorer and other Windows Azure Storage Explorers.
- You can write your own solutions, using information from "Introducing Asynchronous Cross-Account Copy Blob."