0% found this document useful (0 votes)
10 views3 pages

Azure Basic 17

The document outlines the capabilities of Azure storage, including the ability to map drives with SAS and manage share level permissions through various inbuilt roles. It details the tools available for data protection in Azure Files, such as soft delete and snapshots, and describes the types of Azure storage including Blob, File, Disk, Queue, and Table storage. Additionally, it explains the different blob types, access levels, and storage tiers, emphasizing the cost implications of accessing data based on the chosen tier.
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
0% found this document useful (0 votes)
10 views3 pages

Azure Basic 17

The document outlines the capabilities of Azure storage, including the ability to map drives with SAS and manage share level permissions through various inbuilt roles. It details the tools available for data protection in Azure Files, such as soft delete and snapshots, and describes the types of Azure storage including Blob, File, Disk, Queue, and Table storage. Additionally, it explains the different blob types, access levels, and storage tiers, emphasizing the cost implications of accessing data based on the chosen tier.
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/ 3

Tips

● Can I use SAS to map a drive?


a. It is possible to map a drive with SAS.
● Can we provide share level permissions? What are inbuilt roles?
a. Storage File Data SMB Share Reader – Allows READ access
b. Storage File Data SMB Share Contributor – Allows read, write, delete access
c. Storage File Data SMB Share Elevated Contributor - Allows read, write, delete,
and
modify Windows ACLs.
Configure snapshots and soft delete for Azure
Files
Azure Files will have a few tools to protect your data, those are as follows
1. Soft delete,
2. Snapshots,
3. Azure Backup
4. Azure File Sync.
For more information, please refer to the following links
● Enable soft delete on Azure file shares
● Prevent accidental deletion of Azure file shares.
● Enable soft delete for Azure Files | Microsoft Learn
--Back to Index-- 53
For more information, please refer to the following links
● Overview of share snapshots for Azure Files.
● Use Azure Files share snapshots | Microsoft Learn
Azure BLOB
Azure Storage has 5 types:
Azure Blob storage Used to store Binary/Text data
Azure File storage File Shares
Azure Disk Storage Persistent data storage
Azure Queue
Messaging Store and Queuing
storage
Azure Table
NoSQL Datastore
storage
Blob Storage:
● Scalable and It can be used for DR purposes
● Use REST API, CLI, ARM template to create a storage account
● Blob is typically a file, can be image, file, video
● Common scenarios – backup/restore, upload large files, logging
● New version of ADLS (Azure Data Lake Storage) is built on top of Blob called ADLS
Gen2
● Endpoint for Blobs is https://*.blob.core.windows.net
● For a blob, the base URI includes the name of the account (myaccount), the name of
the
container(mycontainer), and the name of the blob(myblob).
Here name will as follows:
https://myaccount.blob.core.windows.net/mycontainer/myblob
● You can use Storage Explorer to view/upload/copy files
Limits:
● No limits to the number of objects
● Max size of a single object in a container is about 5TB
Blob types
● Block Blob – Large objects that are broken and each block is uploaded in
parallel.
It is optimal for Streaming
● Append Blobs – We use these where we keep updating and appending to
the files.
For example, logging.
● Page Blob – Stores the VHD VM disks. Max size is 8TB
Access levels
● Private (no anonymous access) – This is the default. A valid
token is needed to access data.
--Back to Index-- 54
● 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.
Configure storage tiers
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 up.
● You need to decide based on how often you access & balance between storage,
access cost.
● Cool – Use this for more than 30 days but less than 180 days.
● Archive – This is for anything accessed for more than 180 days.
Please note that it will take several hours to access the data.
● To recall, you need to “rehydrate” the blob by changing the access tier to Hot or Cool.
This
can also be set at blob level only, whereas COOL/HOT is at the account level.

You might also like