Scribd
Upload
21 views

Lab15 - Understanding Locally Redundant Storage (LRS) - 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 DOCX, PDF, TXT or read online on Scribd
21 views

Lab15 - Understanding Locally Redundant Storage (LRS) - 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 DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 29

Cloud Computing - Azure

Lab15 – Understanding Local Redundant Storage (LRS) - Azure

Locally redundant storage (LRS): (Low-cost data redundancy)

Locally redundant storage (LRS) provides at least 99.999999999% (11 nines)


durability of objects over a given year. LRS provides this object durability by
replicating your data to a storage scale unit. A datacenter, located in the
region where you created your storage account, hosts the storage scale unit.
A write request to an LRS storage account returns successfully only after the
data is written to all replicas. Each replica resides in separate fault domains
and update domains within a storage scale unit.

A storage scale unit is a collection of racks of storage nodes. A fault domain


(FD) is a group of nodes that represent a physical unit of failure. Think of a
fault domain as nodes belonging to the same physical rack. An upgrade
domain (UD) is a group of nodes that are upgraded together during the
process of a service upgrade (rollout). The replicas are spread across UDs
and FDs within one storage scale unit. This architecture ensures your data is
available if a hardware failure affects a single rack or when nodes are
upgraded during a service upgrade.

LRS is the lowest-cost replication option and offers the least durability
compared to other options. If a datacenter-level disaster (for example, fire or
flooding) occurs, all replicas may be lost or unrecoverable. To mitigate this
risk, Microsoft recommends using either zone-redundant storage (ZRS) or
geo-redundant storage (GRS).

 If your application stores data that can be easily reconstructed if data


loss occurs, you may opt for LRS.
 Some applications are restricted to replicating data only within a
country due to data governance requirements. In some cases, the
paired regions across which the data is replicated for GRS accounts may
be in another country.

Page 1 of 29
Cloud Computing - Azure

Topology

Page 2 of 29
Cloud Computing - Azure

Locally Redundant Storage (Back-End):

Page 3 of 29
Cloud Computing - Azure

In Azure portal, click “Resource groups”.

Page 4 of 29
Cloud Computing - Azure

Click “Add”.

Page 5 of 29
Cloud Computing - Azure

While create “Resource group”

Type “Resource group name” as “SansboundAzureClass”.

Select “Subscription” as “Free Trial”.

Select “Resource group location” as “Central US”.

Click “Create”.

Page 6 of 29
Cloud Computing - Azure

Click “Storage accounts” in left side panel.

Page 7 of 29
Cloud Computing - Azure

In “Storage accounts”.

Click “Add”.

Page 8 of 29
Cloud Computing - Azure

Select “Subscription” as “Free Trial”.

Select “Resource group” as ”SansboundAzureClass”.

Type “Storage account name” as “sansboundlrs”.

Select “Location” as “Central US”.

In “Performance” click ”Standard”.

Select “Account kind” as “Storage (general purpose v2)”.

Select “Replication” as “Locally-redundant-storage (LRS)”.

Page 9 of 29
Cloud Computing - Azure

Click “Next : Advanced >”.

Page 10 of 29
Cloud Computing - Azure

In “Advanced”,

Click “Next : Tags >” .

Page 11 of 29
Cloud Computing - Azure

In “Tags”,

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

Page 12 of 29
Cloud Computing - Azure

Click “Next : Review + create”.

Page 13 of 29
Cloud Computing - Azure

Click “Create”.

Page 14 of 29
Cloud Computing - Azure

Click “Go to resource”.

Page 15 of 29
Cloud Computing - Azure

In “sansboundblob”.

Click “Blobs”.

Page 16 of 29
Cloud Computing - Azure

In “Blobs”.

Click “Container” to create container.

Page 17 of 29
Cloud Computing - Azure

While create new container,

In “Name” type name as “sansboundblob”.

In “Public access level” select as “Blob”.

Page 18 of 29
Cloud Computing - Azure

Click “Ok”.

Page 19 of 29
Cloud Computing - Azure

Click container named “sansboundblob”.

Page 20 of 29
Cloud Computing - Azure

Click “Upload”.

Page 21 of 29
Cloud Computing - Azure

In “Upload blob”

Click “Icon”.

Page 22 of 29
Cloud Computing - Azure

Locate the path of index.html file where you have stored and select “index.html” file.

Click “Open”.

Page 23 of 29
Cloud Computing - Azure

Click “Upload”.

Page 24 of 29
Cloud Computing - Azure

Click “index.html”.

Page 25 of 29
Cloud Computing - Azure

Click “Generate SAS”.

Page 26 of 29
Cloud Computing - Azure

Click “Generate blob SAS token and URL”.

Page 27 of 29
Cloud Computing - Azure

In “Blob SAS URL”

Click “Icon” to copy Blob SAS URL path.

Page 28 of 29
Cloud Computing - Azure

Paste “Blob URL” in browser and press “Enter”

Note: Your data has been stored in same region in same availability zone in different storage nodes. If
primary node failed, then you can able to access data from Secondary node.

Page 29 of 29

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy