Scribd
Upload
20 views

Lab16 - Understanding Zone Redundant Storage (ZRS) - Azure

Uploaded by

raj0000kaml
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
20 views

Lab16 - Understanding Zone Redundant Storage (ZRS) - Azure

Uploaded by

raj0000kaml
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Cloud Computing - Azure

Lab16 – Understanding Zone-Redundant Storage (ZRS) - Azure


Zone Redundant Storage (ZRS)

Zone-redundant storage (ZRS) replicates your data synchronously across three storage
clusters in a single region. Each storage cluster is physically separated from the others
and is located in its own availability zone (AZ). Each availability zone—and the ZRS
cluster within it—is autonomous and includes separate utilities and networking features.

When you store your data in a storage account using ZRS replication, you can continue
to access and manage your data if an availability zone becomes unavailable. ZRS
provides excellent performance and low latency. ZRS offers the same scalability
targets as locally redundant storage (LRS).

Consider ZRS for scenarios that require consistency, durability, and high availability.
Even if an outage or natural disaster renders an availability zone unavailable, ZRS offers
durability for storage objects of at least 99.9999999999% (12 9's) over a given year.

For more information about availability zones, see Availability Zones overview.

Support coverage and regional availability

ZRS currently supports standard general-purpose v2 account types. For more


information about storage account types, see Azure storage account overview.

ZRS is available for block blobs, non-disk page blobs, files, tables, and queues.

ZRS is generally available in the following regions:

 US East
 US East 2
 US West 2
 US Central
 North Europe
 West Europe
 France Central
 Southeast Asia

Page 1 of 17
Cloud Computing - Azure

Topology

Page 2 of 17
Cloud Computing - Azure

Back-End Topology (ZRS):

Page 3 of 17
Cloud Computing - Azure

In Azure portal, click “Resource groups”.

Page 4 of 17
Cloud Computing - Azure

In “Resource groups” click “Add”.

Page 5 of 17
Cloud Computing - Azure

In “Resource group name”,

Type “Resource group name” as “SansboundAzureClass”.

Select “Subscription” as “Free Trial”.

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

Page 6 of 17
Cloud Computing - Azure

Click “Create”.

Page 7 of 17
Cloud Computing - Azure

In Azure portal, click “Storage accounts”.

Page 8 of 17
Cloud Computing - Azure

Click “Add”.

Page 9 of 17
Cloud Computing - Azure

While create storage account,

Select “Subscription” as “Free Trial”.

Select “Resource group” as “SansboundAzureClass”.

Type “Storage account name” as “sansboundblob”.

Select “Location” as “Central US”.

Select “Performance” as “Standard”.

Select “Account kind” as “Storage V2”.

Select “Replication” as “Zone Redundant storage”.

Select “Access tier” as “Hot”.

Page 10 of 17
Cloud Computing - Azure

Click “Next : Advanced >”.

Page 11 of 17
Cloud Computing - Azure

Click “Next : Tags >”.

Page 12 of 17
Cloud Computing - Azure

In “Tags”,

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

Page 13 of 17
Cloud Computing - Azure

Click “Next : Review + create”.

Page 14 of 17
Cloud Computing - Azure

Click “Create”.

Page 15 of 17
Cloud Computing - Azure

Click “Go to resource”.

Page 16 of 17
Cloud Computing - Azure

In “sansboundblob” storage account, click blobs.

Then create container and upload the files into the container.

Note : Whatever the data you have stored in that container it will kept three copies in each Availability
zone. If the Availability Zone – A fails, then you can able to access data from Availability Zone – B.
That’s the reason we have preferred Zone-based Redundant Storage.

Page 17 of 17

You might also like