Description of the azure storage account

All Azure Story artifacts are included in the Azure Storage account: blobs, directories, queues, tables, and drives. The storage account provides a unique namespace for your Azure Storage data, which can be accessed through HTTP or HTTPS from all over the world. Data is long-term and highly available and protected and huge, on your Azure Storage Account.

Types of storage accounts

Azure Storage provides multiple storage accounts. Every category has its own price model and supports different characteristics. Remember these variations before you set up a space account for your applications to decide the type of account you want. Space accounts are of the following kind:

Storage Account Types

Description

Price

General-purpose v2 accounts: 

Blobs, files, queues, and tables are the basic storage account sort. Suitable for most Azure Storage scenarios.

$0.001/GB per month

General-purpose v1 accounts:

Blobs, directories, queues, and tables Legacy account sort. When necessary, instead, using v2 general-purpose accounts.

$0.001/GB per month

BlockBlobStorage accounts: 

Blob-only storage accounts with high-quality features. Suited for high transaction rate situations, use of smaller objects or consistently low latency processing.

$0.001/GB per month

FileStorage accounts: 

The space file only accounts for higher quality functionality. Recommended for businesses and projects with high performance.

$0.058/GB per month

blob storage accounts: 

Legacy space accounts for Blob only. If necessary, instead use general v2 accounts.

$0.001/GB per month

Replication

Replication options for a storage account include:

Locally redundant storage (LRS): A quick, low-cost strategy for replication. In the primary field, the data are synchronously repeated three times.

Zone-redundant storage (ZRS): Replication of high-availability situations. Three Azure available zones in the primary area duplicate their data synchronously.

Geo-redundant storage (GRS): Cross-regional replication to eliminate territorial breakdowns. Data is repeated in the primary region synchronously three times, then replicated in a secondary region asynchronously. Allow read-access geo-redundant (RA-GRS) storage to secondary area data.

Geo-zone-redundant storage (GZRS) (preview): Scenarios that require high availability, as well as total reliability, are repeated. Three Azure availability areas in the primary region merge data synchronously and propagate asynchronously into the secondary zone. Enable read-access geo-zone-redundant (RA-GZRS) storage for the secondary area data.

Data redundancy options

locally redundant storage

Designed to ensure the longevity of objects for at least 99,9999999 (11 9's) for one year by keeping several copies of your information in one data center.

zone redundant storage

Designed for minimum durability of 99,99999999% (12 9's), by keeping multiple copies of your data through several datacenters and regions over a given year.

geographically redundant storage

Determined to ensure that the period of events over a given year is at least 99.999999999 (169 9) by maintaining multiple copies of this information in a particular region and to a synchronized them into a second region.

read access geographically redundant storage

Designed to provide durability for items of at least 99,999,99999% (16 9's) over a given year and 99,99% read accessibility by allowing GRS to access reading from the second area.

General v2 storage accounts embrace the new Azure Storage enhancements and add both general v1 and blob storage accounts functionality. For the majority of storage scenarios, general v2 accounts are recommended. Overall v2 accounts provide both the lowest capacity prices per gigabyte for Azure Storage and industry-competitive prices for transactions. The default account access levels between hot or cool and blob levels tier between hot, cool, or argue are supported by general v2 accounts. Modify your v1 or Blob storage accounts to a general v2 storage account is fast. The Azure server, PowerShell or Azure CLI can be used to update. Upgrading the v1 or Blob storage account to the v2 user account is irreversible and cannot be reversed.

For converting a general v1 account with PowerShell into a general v2 account, first, upgrade PowerShell to use the new Az. Storage module version.

The following command will then be called in order to upgrade your account, to remove the name of your resource class, the account name and the access level you want to use.

Set-AzStorageAccount -ResourceGroupName <resource-group> -AccountName <storage-account> -UpgradeToStorageV2 -AccessTier <Hot/Cool>

General Accounts v2 support all Azure storage resources and data objects, but only block blocks within Blob storage can reach third parties. When upgrading to a general v2 storage account, you can set the default hot or cool access tier for an account that says your blob is the default tier that will upload your blob data as if the parameter for a blob access tier was not specified.

The access rates from Blob allow you to pick the most economic space on the basis of the usage patterns you expect. You will store the block blobs in a warm, cool or archive stage.

The warm access rate creates a new storage account by default and the general v1 storage account can be changed to either the hot or cool account level. If an access level on an account is not specified for the upgrade, the default is dry. Consider your current usage scenario when you are exploring which level of access to be used for your upgrade.