Practical No. 35
Aim: To create storage account.
Step1: Create storage account
For Basic:
Storage Account Name – storageaccountshahira Performance – Standard  Redundancy –GZRS
For Advance:
Allow enabling anonymous access on individual container.
Step2: Create container
Go to storageaccountshahira  container  container  Name – container1  Anonymous access
level – private  create
Upload a file in a container1
 To lock the delete option for a specific file  select the file and Acquire lease.
 To unlock the delete option for a specific file  select the file and Break lease.
 If we copy the URL of a specific file & paste it on internet then we are unable to get the
access as it is private ( Anonymous access level)
 To get access on the internet change the access level to container & you will be able to see
the file on internet.
For Snapshot:
 Go to storageaccountshahira  container1  file name “Shahira”  edit  save  Snapshot
 Create Snapshot
 We can edit n number of time & create snapshot but if we feel any of the previous version
were better than new one….. select the version and promote it we will be able to view it in
edit tab.
For Versioning:
 Go to storage account  storageaccountshahira  overview  Blog services  Versioning
– Tracking – Enable versioning for blobs – tick – enable
 Go to storage account  storageaccountshahira  container1  Select the file name
“shahira”  edit – save  version
 If we feel any of the previous version were better than new one….. select the version &
make current version.
 If a file is deleted then it can be recovered by versioning.
Storage Account
General Purpose 2
less iops throughput
+ high latency =
low performance
Binary Large
Object
Standard
(HDD)
Blob
Premium (SSD)
File Share
Store File
Block
Blob
Apend
Blob
Queues
Tables
Store
Message
Store No SQL
Database
Page
Blob
Block Blob
Logging
Data
Unstructured
Data
Page Blob
File Share
Data
Disk
User create
User delete
Stop VM
Start VM
Size:
(190.7 TB)
Image
Video
General Purpose 2
more iops throughput
+ low latency =
high performance
On Premises
Azure
Sever1
Ways to
Transfer Data
Migration
Storage
Account
VM1
OSD
OSD
Block
Object
For Blocks: Random data will be transfer as well
as no confirmation that data will be send
1
4
7
2
5
8
1
3
6
9
7
2
5
8
6
Transfer
For Object: Complete data will be transfer as well
as with confirmation that data will be send
Transfer
Sever2
OSD
V Net
OSD from the Server 1 which
was on On Premises will
migrating to azure it will stored
in storage account.
Further will storing to VM it
will act as a Data Disk.
OSD
OSD
Data Disk
VM2
OSD
OSD
OSD
Data Disk
Locally redundant storage (LRS)
storageaccountmulund
Standard Performance
1 blobs
2 files
3 queues
4 tables
Central India
Data Center
Rack1
Rack2
Rack3
SA1
SA 2
SA 3
 In LRS there is a V Net which contain one data center with 3 rack it in. Each rack has an
image which is unstructured data that is stored in block blob.
 If one rack has a failure then other rack will overtake the load. But in case all the rack has a
failure that is the entire data center then the data will be lost.
 This is not used to critical data.
 3 copies stored in a single Datacenter. Single point of failure if the data center is unavailable.
Cheapest option.
Geo-redundant storage (GRS)
storageaccountmulund
Central India
Standard Performance
Data Center
1 blobs
2 files
3 queues
4 tables
Read + Write
Primary Region
Synchronous
Rack1
Rack2
Rack3
SA 1
SA 2
SA 3
Secondary Region
Asynchronous
West India
Read if tick
 In GRS, if 1 data center is working
properly then we can access the
other data center to read only if the
above sentence is tick.
 If the 1st data center has a failure
then the other data center get the
permission to read and write.
Data Center
Rack1
Rack2
Rack3
SA 1
SA 2
SA 3
 Here, the secondary copies are stored in another region, which protects us against a regionwide outage. Basically, it is LRS plus an additional copy in a secondary region. The primary
copy process is Synchronous, while it is asynchronous for secondary.
 Read-access geo-redundant storage (RA-GRS) – Compared with GRS, the secondary copy
will also be available only for READ access.
Zone-redundant storage (ZRS)
storageaccountmulund
Central India
Standard Performance
Zone1
Data Center
1 blobs
2 files
3 queues
4 tables
Zone 2
Zone 3
Data Center
Data Center
Rack
Rack
Rack
SA
SA
SA
 3 copies in 3 zones in the primary region. Also recommended to replicate to the secondary
region.
Zone-redundant storage (ZRS)
Primary Region
Synchronous
Central India
storageaccountmulund
Zone 1
Zone 2
Zone 3
Standard Performance
Data Center
Data Center
Data Center
1 blobs
2 files
3 queues
4 tables
Write + Read
Read if tick
Rack
Rack
Rack
SA
SA
SA
Secondary Region
Asynchronous
West India
Data Center
Rack
Rack
Rack
SA
SA
SA
 Geo-zone-redundant storage (GZRS) – Here, it is the same as LRS except that the secondary
copy will be in a zone in another region, which is the twin region of our primary region.
Basically, it is ZRS plus a single copy in the secondary region. The primary copy process is
Synchronous, while it is asynchronous for secondary.
 Read-access geo-zone-redundant storage (RA-GZRS) – Same as GZRS, except that you will be
able to read data from your secondary region also. (If it is not RA, then we need to
remember that data is available but not readable until Microsoft fails over to the secondary
region in case of a regional failure or if we manually failover)
Access levels:
 Private (no anonymous access) – This is the default. A valid token is needed to access data.
 Blob (anonymous read access for blobs only) – Globally accessible with reading access.
 Container (anonymous read access for containers and blobs) – All blobs in the container can
be read and listed. Access is at the container level, and hence it is for container level, and
every blob can be read.
Access Tiers:
 There are 3 access tiers – Hot/Cool and Archive.
 As you move from Archive to hot, the pricing will go up, and as you move from Hot to
Archive, the cost of accessing will go down.
 You need to decide based on how often you access and balance between storage cost and
access cost.
 Hot/Hot (Inferred) – Store information which data is accessed frequently.
 Cool/Cold – Store information which data is accessed less frequently. Use this for more than
30 days but less than 180 days
 Archive – Store information which data is accessed rarely. This is for anything accessed for
more than 180 days. Please note that it will take several hours to access the data.
Soft Delete:




If you enable this feature, the blob will not be deleted but will be marked for deletion.
You specify the number of days, like 90, and after 90 days, the blobs will be deleted.
This protects against malicious or accidental deletion.
Please note that you will pay for the 90 days of storage.
NOTE:
 To lock the delete option for a specific file  select the file and Acquire lease.
 To unlock the delete option for a specific file  select the file and Break lease.
Storage Account (Standard General Purpose 2)
storageaccountshahira
Blob (Container) Soft delete – 7days
Blob blobs
Soft delete – 7days
File Share
Queues
Tables