Azure Stroage Cost Estimation

%3CLINGO-SUB%20id%3D%22lingo-sub-1061943%22%20slang%3D%22en-US%22%3EAzure%20Stroage%20Cost%20Estimation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1061943%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Team%2C%20we%20have%20a%20requirement%20to%20copy%20atleast%2050%20TB%20of%20data%20to%20Azure%20Storage%20Account%20in%20Cool%20or%20an%20Archive%20Tier%20initially%20and%20then%20we%20will%20be%20copying%202%20TB%20every%20month.%26nbsp%3B%20And%20the%20retrieval%20is%20when%20ever%20its%20needed%20and%20we%20can%20wait%20max%20of%207%20days.%3C%2FP%3E%3CP%3ESo%20what%20i%20am%20looking%20is%20the%20storage%20cost%20for%20storing%20and%20retrieving%20the%20data%20whenever%20i%20needed.%20I%20am%20using%20the%20azure%20pricing%20calculator%20and%20there%20is%20something%20where%20we%20need%20to%20feed%20in%20for%20the%20operations%20and%20i%20am%20not%20sure%20how%20i%20can%20calculate%20the%20no%20of%20write%20or%20read%20operations.%20I%20am%20looking%20for%20a%20help%20on%20the%20same.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20attaching%20the%20screenshot%20which%20i%20started%20filling.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F161311i0E45A37C17D26510%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1061943%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Storage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1062322%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Stroage%20Cost%20Estimation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1062322%22%20slang%3D%22en-US%22%3EI%20have%20shared%20a%20link%20here%2C%20which%20describe%20the%20capacity%20planning%20on%20azure%20storage%20account.%20Hope%20this%20will%20clear%20your%20doubts.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.msdn.microsoft.com%2Fwindowsazurestorage%2F2010%2F07%2F08%2Funderstanding-windows-azure-storage-billing-bandwidth-transactions-and-capacity%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.msdn.microsoft.com%2Fwindowsazurestorage%2F2010%2F07%2F08%2Funderstanding-windows-azure-storage-billing-bandwidth-transactions-and-capacity%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1062515%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Stroage%20Cost%20Estimation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1062515%22%20slang%3D%22en-US%22%3EHello%20Vinoth%2C%20Thanks%20for%20your%20article.%3CBR%20%2F%3Ewhat%20i%20understood%20is%3CBR%20%2F%3E1.%20Each%20block%20size%20will%20be%2032%20MB%20(so%20for%20any%20operation%20we%20should%20divide%20the%20file%20size%20with%2032%20GB)%20and%20it%20will%20be%20those%20many%20operations%3CBR%20%2F%3E2.%20but%20my%20confusion%20here%20is%20the%20second%20part%20of%20the%20article%20where%20it%20is%20talking%20about%20the%20name%2C%20so%20can%20you%20please%20let%20me%20know%20how%20i%20should%20interpret%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20referring%20to%20this%20section%3CBR%20%2F%3EFor%20Block%20Blob%20(base%20blob%20or%20snapshot)%20we%20have%3A%3CBR%20%2F%3E124%20bytes%20%2B%20Len(BlobName)%20*%202%20bytes%20%2B%3CBR%20%2F%3EFor-Each%20Metadata%5B3%20bytes%20%2B%20Len(MetadataName)%20%2B%20Len(Value)%5D%20%2B%3CBR%20%2F%3E8%20bytes%20%2B%20number%20of%20committed%20and%20uncommitted%20blocks%20*%20Block%20ID%20Size%20in%20bytes%20%2B%3CBR%20%2F%3ESizeInBytes(data%20in%20committed%20and%20uncommitted%20data%20blocks)%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20in%20advance.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

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 ever its needed and we can wait max of 7 days.

So what i am looking is the storage cost for storing and retrieving the data whenever i needed. I am using the azure pricing calculator and there is something where we need to feed in for the operations and i am not sure how i can calculate the no of write or read operations. I am looking for a help on the same. 

I am attaching the screenshot which i started filling.

 

clipboard_image_0.png

2 Replies
Highlighted
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-...
Highlighted
Hello 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.