Scribd
Upload
39 views20 pages

Lab17 - Understanding Geo Redundant Storage (GRS) - Azure

Uploaded by

raj0000kaml
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
39 views20 pages

Lab17 - Understanding Geo Redundant Storage (GRS) - Azure

Uploaded by

raj0000kaml
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Cloud Computing - Azure

Lab17 – Understanding Geo-Redundant Storage (GRS) - Azure

Geo-redundant storage (GRS)

Geo-redundant storage (GRS) is designed to provide at least 99.99999999999999% (16


9's) durability of objects over a given year by replicating your data to a secondary region
that is hundreds of miles away from the primary region. If your storage account has GRS
enabled, then your data is durable even in the case of a complete regional outage or a
disaster in which the primary region isn't recoverable.

If you opt for GRS, you have two related options to choose from:

 GRS replicates your data to another data center in a secondary region, but that
data is available to be read only if Microsoft initiates a failover from the primary to
secondary region.
 Read-access geo-redundant storage (RA-GRS) is based on GRS. RA-GRS replicates
your data to another data center in a secondary region, and also provides you with
the option to read from the secondary region. With RA-GRS, you can read from the
secondary region regardless of whether Microsoft initiates a failover from the
primary to secondary region.

For a storage account with GRS or RA-GRS enabled, all data is first replicated with locally
redundant storage (LRS). An update is first committed to the primary location and
replicated using LRS. The update is then replicated asynchronously to the secondary
region using GRS. When data is written to the secondary location, it's also replicated
within that location using LRS.

Both the primary and secondary regions manage replicas across separate fault domains
and upgrade domains within a storage scale unit. The storage scale unit is the basic
replication unit within the datacenter. Replication at this level is provided by LRS; for
more information, see Locally redundant storage (LRS): Low-cost data redundancy for
Azure Storage.

Keep these points in mind when deciding which replication option to use:

 Zone-redundant storage (ZRS) provides highly availability with synchronous


replication and may be a better choice for some scenarios than GRS or RA-GRS.
For more information on ZRS, see ZRS.

Page 1 of 20
Cloud Computing - Azure

 Asynchronous replication involves a delay from the time that data is written to the
primary region, to when it is replicated to the secondary region. In the event of a
regional disaster, changes that haven't yet been replicated to the secondary region
may be lost if that data can't be recovered from the primary region.
 With GRS, the replica isn't available for read or write access unless Microsoft
initiates a failover to the secondary region. In the case of a failover, you'll have
read and write access to that data after the failover has completed. For more
information, please see Disaster recovery guidance.
 If your application needs to read from the secondary region, enable RA-GRS.

is designed to provide at least 99.99999999999999% (16 9's) durability of objects over a


given year by replicating your data to a secondary region that is hundreds of miles away
from the primary region. If your storage account has GRS enabled, then your data is
durable even in the case of a complete regional outage or a disaster in which the
primary region isn't recoverable.

If you opt for GRS, you have two related options to choose from:

 GRS replicates your data to another data center in a secondary region, but that
data is available to be read only if Microsoft initiates a failover from the primary to
secondary region.
 Read-access geo-redundant storage (RA-GRS) is based on GRS. RA-GRS replicates
your data to another data center in a secondary region, and also provides you with
the option to read from the secondary region. With RA-GRS, you can read from the
secondary region regardless of whether Microsoft initiates a failover from the
primary to secondary region.

For a storage account with GRS or RA-GRS enabled, all data is first replicated with locally
redundant storage (LRS). An update is first committed to the primary location and
replicated using LRS. The update is then replicated asynchronously to the secondary
region using GRS. When data is written to the secondary location, it's also replicated
within that location using LRS.

Both the primary and secondary regions manage replicas across separate fault domains
and upgrade domains within a storage scale unit. The storage scale unit is the basic
replication unit within the datacenter. Replication at this level is provided by LRS; for
more information, see Locally redundant storage (LRS): Low-cost data redundancy for
Azure Storage.

Page 2 of 20
Cloud Computing - Azure

Keep these points in mind when deciding which replication option to use:

 Zone-redundant storage (ZRS) provides highly availability with synchronous


replication and may be a better choice for some scenarios than GRS or RA-GRS.
For more information on ZRS, see ZRS.
 Asynchronous replication involves a delay from the time that data is written to the
primary region, to when it is replicated to the secondary region. In the event of a
regional disaster, changes that haven't yet been replicated to the secondary region
may be lost if that data can't be recovered from the primary region.
 With GRS, the replica isn't available for read or write access unless Microsoft
initiates a failover to the secondary region. In the case of a failover, you'll have
read and write access to that data after the failover has completed. For more
information, please see Disaster recovery guidance.
 If your application needs to read from the secondary region, enable RA-GRS.

Page 3 of 20
Cloud Computing - Azure

Topology:

Page 4 of 20
Cloud Computing - Azure

Back-End Topology (GRS):

Page 5 of 20
Cloud Computing - Azure

In Azure portal, click “Resource groups”.

Page 6 of 20
Cloud Computing - Azure

Click “Add”.

Page 7 of 20
Cloud Computing - Azure

While create “Resource group”

It requires “Resource group name”, type “SansboundAzureClass”.

In “Subscription“, select “Free Trial”.

In “Resource group location”.

Page 8 of 20
Cloud Computing - Azure

Click “Create”.

Page 9 of 20
Cloud Computing - Azure

Click “Storage accounts” in left side panel.

Page 10 of 20
Cloud Computing - Azure

Click “Add”.

Page 11 of 20
Cloud Computing - Azure

While create storage account,

Select “Susbscription” as “Free Trial”.

Select “Resource group” as “SansboundAzureClass”.

In Storage account name “sansboundblob”.

Select “Location” as “Central US”.

Select “Performance” as “Standard”.

Select “Account kind” as “Storage V2”.

Select “Replication” as “Geo-redundant storage (GRS)”.

Set “Access Tier” as “Hot”.

Page 12 of 20
Cloud Computing - Azure

Click “Next : Advanced >”.

Page 13 of 20
Cloud Computing - Azure

Click “Next : Tags >”.

Page 14 of 20
Cloud Computing - Azure

In “Tags”,

Type “KEY” as “Name” and “VALUE” as “Sansbound-Storage”.

Page 15 of 20
Cloud Computing - Azure

Click “Next : Review + create”.

Page 16 of 20
Cloud Computing - Azure

Click “Create”.

Page 17 of 20
Cloud Computing - Azure

Click “Go to resource”.

Page 18 of 20
Cloud Computing - Azure

In “sansboundblob”,

Click “Blobs”.

Page 19 of 20
Cloud Computing - Azure

Click “Container” to create container and upload the files in container.

Note: Whatever the files upload into the container backup copy also available nearest geographical
Region as backup. In case of “Region -1” was down, you can able to access the files from Region -2.

Page 20 of 20

You might also like