0% found this document useful (0 votes)
20 views

Lab13 - Understanding Azure Files Storage - 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
0% found this document useful (0 votes)
20 views

Lab13 - Understanding Azure Files Storage - 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/ 70

Cloud Computing - Azure

Lab13 – Understanding Azure Files Storage - Azure

Azure Storage provides three types of storage accounts. Each type


supports different features and has its own pricing model. Consider these
differences before you create a storage account to determine the type of
account that is best for your applications. The types of storage accounts are:

 General-purpose v2 accounts (recommended for most scenarios)


 General-purpose v1 accounts
 Blob storage accounts

Page 1 of 70
Cloud Computing - Azure

1
Using the Azure Resource Manager deployment model is recommended.
Storage accounts using the classic deployment model can still be created in
some locations, and existing classic accounts continue to be supported. For
more information, see Azure Resource Manager vs. classic deployment:
Understand deployment models and the state of your resources.

2
All storage accounts are encrypted using Storage Service Encryption (SSE)
for data at rest. For more information, see Azure Storage Service Encryption
for Data at Rest.

3
The Archive tier is available at level of an individual blob only, not at the
storage account level. Only block blobs and append blobs can be archived.
For more information, see Azure Blob storage: Hot, Cool, and Archive storage
tiers.

4
Zone-redundant storage (ZRS) is available only for standard general-
purpose v2 storage accounts. For more information about ZRS, see Zone-
redundant storage (ZRS): Highly available Azure Storage applications. For
more information about other replication options, see Azure Storage
replication.

General-purpose v2 accounts

General-purpose v2 storage accounts support the latest Azure Storage


features and incorporate all of the functionality of general-purpose v1 and
Blob storage accounts. General-purpose v2 accounts deliver the lowest per-
gigabyte capacity prices for Azure Storage, as well as industry-competitive
transaction prices. General-purpose v2 storage accounts support these Azure
Storage services:

 Blobs (all types: Block, Append, Page)


 Files
 Disks
 Queues
 Tables

Page 2 of 70
Cloud Computing - Azure

Note

Microsoft recommends using a general-purpose v2 storage account for most


scenarios. You can easily upgrade a general-purpose v1 or Blob storage
account to a general-purpose v2 account with no downtime and without the
need to copy data.

For more information on upgrading to a general-purpose v2 account,


see Upgrade to a general-purpose v2 storage account.

General-purpose v2 storage accounts offer multiple access tiers for storing


data based on your usage patterns. For more information, see Access tiers
for block blob data.

General-purpose v1 accounts

General-purpose v1 accounts provide access to all Azure Storage services,


but may not have the latest features or the lowest per gigabyte pricing.
General-purpose v1 storage accounts support these Azure Storage services:

 Blobs (all types)


 Files
 Disks
 Queues
 Tables

While general-purpose v2 accounts are recommended in most cases,


general-purpose v1 accounts are best suited to these scenarios:

 Your applications require the Azure classic deployment model. General-


purpose v2 accounts and Blob storage accounts support only the Azure
Resource Manager deployment model.
 Your applications are transaction-intensive or use significant geo-
replication bandwidth, but do not require large capacity. In this case,
general-purpose v1 may be the most economical choice.
 You use a version of the Storage Services REST API that is earlier than
2014-02-14 or a client library with a version lower than 4.x, and cannot
upgrade your application.

Page 3 of 70
Cloud Computing - Azure

Azure Files

Azure Files offers fully managed file shares in the cloud that are accessible via the
industry standard Server Message Block (SMB) protocol. Azure file shares can be
mounted concurrently by cloud or on-premises deployments of Windows, Linux, and
macOS. Additionally, Azure file shares can be cached on Windows Servers with
Azure File Sync for fast access near where the data is being used.

Azure file shares can be used to:

 Replace or supplement on-premises file servers:


Azure Files can be used to completely replace or supplement traditional
on-premises file servers or NAS devices. Popular operating systems such
as Windows, macOS, and Linux can directly mount Azure file shares
wherever they are in the world. Azure file shares can also be replicated
with Azure File Sync to Windows Servers, either on-premises or in the
cloud, for performance and distributed caching of the data where it's
being used.

 "Lift and shift" applications:


Azure Files makes it easy to "lift and shift" applications to the cloud that
expect a file share to store file application or user data. Azure Files
enables both the "classic" lift and shift scenario, where both the
application and its data are moved to Azure, and the "hybrid" lift and
shift scenario, where the application data is moved to Azure Files, and
the application continues to run on-premises.

 Simplify cloud development:


Azure Files can also be used in numerous ways to simplify new cloud
development projects. For example:

o Shared application settings:


A common pattern for distributed applications is to have configuration
files in a centralized location where they can be accessed from many
application instances. Application instances can load their
configuration through the File REST API, and humans can access them
as needed by mounting the SMB share locally.

o Diagnostic share:
An Azure file share is a convenient place for cloud applications to
write their logs, metrics, and crash dumps. Logs can be written by the
application instances via the File REST API, and developers can access

Page 4 of 70
Cloud Computing - Azure

them by mounting the file share on their local machine. This enables
great flexibility, as developers can embrace cloud development
without having to abandon any existing tooling they know and love.

o Dev/Test/Debug:
When developers or administrators are working on VMs in the cloud,
they often need a set of tools or utilities. Copying such utilities and
tools to each VM can be a time consuming exercise. By mounting an
Azure file share locally on the VMs, a developer and administrator can
quickly access their tools and utilities, no copying required.

Key benefits

 Shared access. Azure file shares support the industry standard SMB protocol,
meaning you can seamlessly replace your on-premises file shares with Azure
file shares without worrying about application compatibility. Being able to
share a file system across multiple machines, applications/instances is a
significant advantage with Azure Files for applications that need shareability.
 Fully managed. Azure file shares can be created without the need to manage
hardware or an OS. This means you don't have to deal with patching the server
OS with critical security upgrades or replacing faulty hard disks.
 Scripting and tooling. PowerShell cmdlets and Azure CLI can be used to
create, mount, and manage Azure file shares as part of the administration of
Azure applications.You can create and manage Azure file shares using Azure
portal and Azure Storage Explorer.
 Resiliency. Azure Files has been built from the ground up to be always
available. Replacing on-premises file shares with Azure Files means you no
longer have to wake up to deal with local power outages or network issues.
 Familiar programmability. Applications running in Azure can access data in
the share via file system I/O APIs. Developers can therefore leverage their
existing code and skills to migrate existing applications. In addition to System
IO APIs, you can use Azure Storage Client Libraries or the Azure Storage REST
API.

Topology

Page 5 of 70
Cloud Computing - Azure

Page 6 of 70
Cloud Computing - Azure

Back-End Topology:

In Azure portal, click “Resource groups”.

Page 7 of 70
Cloud Computing - Azure

In “Resource groups” click “Add”.

Page 8 of 70
Cloud Computing - Azure

While create “Resource group”

Page 9 of 70
Cloud Computing - Azure

Type “Resource group name” as “SansboundAzureClass”.

In “Subscription” as “Free Trial”.

In “Resource group location” select “South India”.

Click “Create”.

In Dashboard, click “Virtual networks”,

Page 10 of 70
Cloud Computing - Azure

Page 11 of 70
Cloud Computing - Azure

In “Virtual networks” click “Add”.

While create virtual network,

Page 12 of 70
Cloud Computing - Azure

Type “Virtual network name” as “SANS-VNET”.

Type “Address range” as 10.0.0.0/16.

Select “Subscription” as “Free Trial”.

Select “Resource group” as “SansboundAzureClass”.

Select “Location” as “South India”.

In Subnet type “Subnet name” as “Front-EndSubnet”.

Type “Front-EndSubnet” address as 10.0.1.0/24.

Page 13 of 70
Cloud Computing - Azure

Click “Create”.

Click “Virtual machines” in left side panel.

Page 14 of 70
Cloud Computing - Azure

In “Virtual machines”.

Page 15 of 70
Cloud Computing - Azure

Click “Add”.

Type “Virtual machine name” as “WindowsVM-Azure”.

Page 16 of 70
Cloud Computing - Azure

Select “Region” as “South India”.

Select “Image” as “Windows Server 2008 R2”.

Change “VM Size” as “Standard B1s”.

In “Administrator Account”

Page 17 of 70
Cloud Computing - Azure

Type “Username” as sanbound

Type “Password” type password for Windows server.

In “Inbound Port Rules”.

Click “Public inbound ports” as “Allow selected ports”.

“Select inbound ports” as “RDP”.

Page 18 of 70
Cloud Computing - Azure

In “Save Money”.

Click “Yes” for Already have a Windows license.

Need to check “Confirmation” box.

Page 19 of 70
Cloud Computing - Azure

Click “Next : Disks >”.

In “Disks”.

Page 20 of 70
Cloud Computing - Azure

Click “Next : Networking”.

In “Networking”

Page 21 of 70
Cloud Computing - Azure

Ensure the VNET and Subnet details.

Click “Next : Management >”.

In “Management”.

Page 22 of 70
Cloud Computing - Azure

Click “Next : Guest config >”.

Page 23 of 70
Cloud Computing - Azure

Click “Next : Tags >”.

Page 24 of 70
Cloud Computing - Azure

In “Tags”.

Click “Next : Review + create”.

Page 25 of 70
Cloud Computing - Azure

Click “Create”.

Page 26 of 70
Cloud Computing - Azure

Click “All resources”.

In “Dasboard” click ”Storage accounts”.

Page 27 of 70
Cloud Computing - Azure

In “Storage accounts” click “sansboundazureclassdiag”.

Page 28 of 70
Cloud Computing - Azure

In “sansboundazureclassdiag”.

Page 29 of 70
Cloud Computing - Azure

Click “File”.

In “Files”

Page 30 of 70
Cloud Computing - Azure

Click “File share”.

In “File Share”

Page 31 of 70
Cloud Computing - Azure

Type “File share” name as “salesdata”.

Type “Quota” as 5 GiB

Click “Create”.

Page 32 of 70
Cloud Computing - Azure

You have successfully added the File Share.

Page 33 of 70
Cloud Computing - Azure

Click “salesdata”.

Page 34 of 70
Cloud Computing - Azure

In “salesdata” file share click “Properties”.

Page 35 of 70
Cloud Computing - Azure

In “salesdata” – Properties

Click “Icon” to copy the path for “Files” storage.

Page 36 of 70
Cloud Computing - Azure

Click “Storage accounts” in left side panel.

Page 37 of 70
Cloud Computing - Azure

In “Storage accounts” click “storage name”.

Page 38 of 70
Cloud Computing - Azure

Click “Files”.

Page 39 of 70
Cloud Computing - Azure

In “Files”

Click “Access keys” to login credentials of the “Files” storage.

Page 40 of 70
Cloud Computing - Azure

In “Access keys”.

In “Storage account name” click “Icon” to copy.

Page 41 of 70
Cloud Computing - Azure

Copy the “Key” by click “Icon”.

Page 42 of 70
Cloud Computing - Azure

Copy the “connection string” by click “Icon”.

Page 43 of 70
Cloud Computing - Azure

Click “Storage accounts”.

Page 44 of 70
Cloud Computing - Azure

In “Storage accounts”.

Click “sansboundazureclassdiag”.

Page 45 of 70
Cloud Computing - Azure

Click “Files”.

Page 46 of 70
Cloud Computing - Azure

Click “salesdata”.

Page 47 of 70
Cloud Computing - Azure

Click “Upload” to upload data from On premises to Azure Files storage.

Page 48 of 70
Cloud Computing - Azure

In “Upload files”

Click “icon” to select files to upload.

Page 49 of 70
Cloud Computing - Azure

Locate the data in your local drive where you have stored.

Click “Open”.

Page 50 of 70
Cloud Computing - Azure

Click “Upload”.

Page 51 of 70
Cloud Computing - Azure

You have uploaded files from on premises successfully.

In “Files” storage, everyone can able to view the files of other user.

Page 52 of 70
Cloud Computing - Azure

Click “Virtual machines” in left side panel.

Page 53 of 70
Cloud Computing - Azure

In “Virtual machine”.

Click “WindowsVM-Azure”.

Page 54 of 70
Cloud Computing - Azure

Kindly note the Public IP address provided for “Windows Server 2008 R2”.

Page 55 of 70
Cloud Computing - Azure

In your local machine, type “mstsc” in “Run” box and click “Ok”,

Type “Public IP” of Windows server 2008 R2.

Click “Connect”.

Page 56 of 70
Cloud Computing - Azure

Type Username and password for the Windows 2008 Server

Click “Ok”.

Page 57 of 70
Cloud Computing - Azure

Click “Yes”.

Page 58 of 70
Cloud Computing - Azure

From “Access key” you have copied below details to access the “Files” storage from Virtual machine in
Azure.

You can able to access the Files storage from virtual machine by using share path UNC: “\\”

So, you have need to modify the arguments as ‘//” with “\\” and “/” with “\”.

In “Windows 2008 Server R2” Virtual machine,

Page 59 of 70
Cloud Computing - Azure

In “Computer”

Click “Map network drive”.

Remove “https:” from the UNC path copy the “Files” storage as UNC path.

Page 60 of 70
Cloud Computing - Azure

\\sansboundazureclassdiag.file.core.windows.net\salesdata

Map Network drive, in “Folder” paste the UNC path of “Files” Storage.

Check “Connect using different credentials”.

Click “Finish”.

It requires username and password.

In username type Azure\storage name

Our storage name is “sansboundazureclassdiag”.

Page 61 of 70
Cloud Computing - Azure

Our storage name is sansboundazureclassdiag, so i have type username as “Azure\


sansboundazureclassdiag”

Copy the key which you have copied from “Files“ storage and paste it in “password” box.

Page 62 of 70
Cloud Computing - Azure

6fQA3ZUO6UNPS3cQjPK38CKxs2qW3akvDC2T6xaRcHSOhXbzMEQTfArggtvifTjwj0O5KUiECCKZYrS+dYn
knA==

Click “Ok” to map the network path as drive.

You have successfully mapped the “Files” storage in Azure virtual machine.

Page 63 of 70
Cloud Computing - Azure

In “Files” storage I have created one folder named “data” and created one file named “Data1.txt”.

Page 64 of 70
Cloud Computing - Azure

Other users who have accessed this share also can able to access the folder(s) / file(s) of others.

In Dashboard click “Storage accounts”.

Page 65 of 70
Cloud Computing - Azure

In “Storage accounts” click storage account name.

Click “Files”.

Page 66 of 70
Cloud Computing - Azure

Page 67 of 70
Cloud Computing - Azure

Click “salesdata”.

Page 68 of 70
Cloud Computing - Azure

You are able to see the folder named “data” which has been recently created.

Click “data” folder.

Select “Data1.txt” file to Download / Delete.

Page 69 of 70
Cloud Computing - Azure

Note: Administrator have access to view / delete the files / folders in the “Files” storage.

Page 70 of 70

You might also like