Replication to a secondary geographic location is provided with RA-GRS. The customer holds read access to the data, maintained in the secondary location. Access from the primary and the secondary region is possible. RA-GRS is the default option for your storage account on creation.
The following is an overview of the redundancy options in Azure Storage:
|
Replication strategy |
LRS |
ZRS |
GRS |
RA-GRS |
|
Data is replicated across multiple datacenters |
No |
Yes |
Yes |
Yes |
|
Data can be read from the secondary location as well as from the primary location |
No |
No |
No |
Yes |
|
Number of copies of data maintained on separate nodes |
3 |
3 |
6 |
6 |
For our example, we select Locally-redundant storage (LRS), as high durability is not necessary in our example. Let's look at the current settings:
In the example, an existing resource group is used to store the storage account resource. North Europe is used as deployment location as it's the nearest location and will probably have the least latency.
To achieve the same goal using PowerShell with the Azure PowerShell module, the following commands can be used:
New-AzureRmStorageAccount `
-ResourceGroupName 'AzureExamples' `
-Name 'implementingazuredemo' `
-Location 'northeurope' `
-SkuName 'Standard_LRS' `
-Kind 'Storage'
In the previous command, ResourceGroupName is the resource group that the storage account should be deployed to. The Name parameter is the planned name for the storage account, the location parameter is the Azure deployment region, and the SkuName parameter is a mix of the performance and replication settings from the Azure portal. This parameter can take the following values:
- Standard_LRS: Locally redundant storage
- Standard_ZRS: Zone-redundant storage
- Standard_GRS: Geo-redundant storage
- Standard_RAGRS: Read-access geo-redundant storage
- Premium_LRS: Premium locally redundant storage