Articles → MICROSOFT AZURE → Introduction To The Storage Accounts In Azure
Introduction To The Storage Accounts In Azure
Purpose
Services Of Azure
- Blob → Stores unstructured data like objects, images, and videos
- Table → Stores data in tabular format
- Queues → Stores queues used for sending and receiving messages
- File → Used to create file shares
Types Of Storage Accounts
- General purpose v2 accounts → This type of storage account provides blob, file, queue, and table services
- General purpose v1 accounts → This type of storage account provides blob, queue, and table services. This is the older version of the storage account type
- BlockBlobStorage accounts → This type of account is used when you want premium performance for storing blocks and append blobs
- File storage accounts → This type of account is used when you want premium performance for file storage only
- BlobStorage accounts → This is a legacy storage account. It is advisable to use a general-purpose v2 account
Replication In Storage Account
- Locally-redundant storage (LRS) → Here, the data is replicated synchronously 3 times within the physical location of the primary region
- Zone-redundant storage (ZRS) → Here, the data is replicated synchronously 3 times across the availability zones of the primary region. This replication is used to recover the data in case of data center failure
- Geo-redundant storage (GRS) → Here, the data is replicated synchronously 3 times in the primary region and then asynchronously replicated in the second region
- Read Access Geo-redundant storage (RA-GRS) → Here, the data is replicated synchronously 3 times in the primary region and then replicated asynchronously in the second region. The data in the secondary storage is available for read-only purposes
- Geo-Zone-redundant storage (GZRS) → Here, the data is replicated synchronously 3 times across the availability zones of the primary region. Then asynchronously in the second region
- Read Access Geo-Zone-redundant storage (RA GZRS) → Here, the data is replicated synchronously 3 times across the availability zones of the primary region and then asynchronously in the second region. The data in the secondary storage is available for read-only purposes
Access Tiers
- Hot → This is optimized to store the data which is frequently accessed
- Cold → This is optimized to store the data which is infrequently accessed and stored for at least 30 days. This is set at the account level
- Archive → This is optimized to store the data which is rarely accessed and stored for at least 180 days. This is set at the blob level
- The storage cost of the cold tier is less than the hot tier
- The access cost of the cold tier is greater than the hot tier
- When the blob is in the archive tier, you cannot access it. You have to rehydrate the blob first