Forum Discussion
Krishna_Azure
Dec 12, 2019Copper Contributor
Azure Stroage Cost Estimation
Hello Team, we have a requirement to copy atleast 50 TB of data to Azure Storage Account in Cool or an Archive Tier initially and then we will be copying 2 TB every month. And the retrieval is when ...
Vinoth_Azure
Dec 12, 2019MCT
I have shared a link here, which describe the capacity planning on azure storage account. Hope this will clear your doubts.
https://blogs.msdn.microsoft.com/windowsazurestorage/2010/07/08/understanding-windows-azure-storage-billing-bandwidth-transactions-and-capacity/
https://blogs.msdn.microsoft.com/windowsazurestorage/2010/07/08/understanding-windows-azure-storage-billing-bandwidth-transactions-and-capacity/
- Krishna_AzureDec 12, 2019Copper ContributorHello Vinoth, Thanks for your article.
what i understood is
1. Each block size will be 32 MB (so for any operation we should divide the file size with 32 GB) and it will be those many operations
2. but my confusion here is the second part of the article where it is talking about the name, so can you please let me know how i should interpret this.
I am referring to this section
For Block Blob (base blob or snapshot) we have:
124 bytes + Len(BlobName) * 2 bytes +
For-Each Metadata[3 bytes + Len(MetadataName) + Len(Value)] +
8 bytes + number of committed and uncommitted blocks * Block ID Size in bytes +
SizeInBytes(data in committed and uncommitted data blocks)
Thanks in advance.