In this
article we will learn about Azure Disk storage account in azure.
•Azure managed disks are block-level storage volumes that are managed by
Azure and used with Azure Virtual Machines.
•Managed disks are like a physical disk in an on-premises server but,
virtualized.
For creating a managed disk, all you have to do is specify the disk
size, the disk type, and provision the disk.
Once you provision the disk, Azure handles the rest.
Types of the
Disk
ØUnmanaged Disk
It is a traditional type of disk that has been used by
VMs. With these disks, we can create our storage account and specify that
storage account when we create the disk. We must not put too many disks in the
same storage account, resulting in the VMs being throttled.
ØManaged
disks:
It handles the storage account creation/management in the
background for us and ensures that we do not have to worry about the
scalability limits of the storage account. We specify the disk size and the
performance tier (standard/premium), and Azure creates and manages the disk for
us.
Ultra Disk :- IO-intensive
workloads such as SAP HANA, top tier databases (for example, SQL, Oracle),
and other transaction-heavy workloads.
Standard HDD disks: It
delivers cost-effective storage. It can be replicated locally in one
data-center, or be geo-redundant with primary and secondary data centers.
Standard SDD disks: It
is designed to address the same kind of workloads as standard HDD disks, but
offer more consistent performance and reliability than HDD. It is suitable for
applications like web servers that do not need high IOPS on disks.
Premium SSD disks: It
is backed by SSDs, and delivers high-performance, low-latency disk support for
VMs running I/O-intensive workloads. The premium SSD disks are mainly used for
production and database servers. So if we are hosting a database in a
particular server, then the premium SSD will be a good option.
Disk type comparison
The following table provides a comparison of the four disk types to help you decide which to use.
Ultra disk
Premium SSD
Standard SSD
Standard HDD
Disk type
SSD
SSD
SSD
HDD
Scenario
IO-intensive workloads such as SAP HANA, top tier databases (for example, SQL, Oracle), and other transaction-heavy workloads.
Production and performance sensitive workloads
Web servers, lightly used enterprise applications and dev/test
Backup, non-critical, infrequent access
Max disk size
65,536 gibibyte (GiB)
32,767 GiB
32,767 GiB
32,767 GiB
Max throughput
4,000 MB/s
900 MB/s
750 MB/s
500 MB/s
Max IOPS
160,000
20,000
6,000
2,000
benefits
of using managed disks.
Highly durable and available
Ømanaged disks are designed for 99.999% availability
ØManaged disks achieve this by providing you with three
replicas of your data, allowing for high durability.
ØThis type of durability protects you from not only
one, but two failures of disk replicas.
Simple
and scalable VM deployment
ØUsing managed disks, you can create up to 50,000 VM
disks of a type in a subscription per region,
ØThis allows you to create thousands of virtual
machines in one subscription.
Øyou can create VM scale sets that include up to 1000
VMs per set, provided you use a marketplace image.
Integration
with availability sets
Ømanaged disks are integrated with both availability
sets and availability zones.
ØThe integration with availability sets ensures that VM
disks within an availability set are isolated from one another.
ØThis protects your applications from a single point of
failure within an Azure datacenter.
ØAvailability zone integration protects applications
from entire Azure datacenter failures.
Azure
Backup support
ØSince Azure backup supports the backup and restore of
managed disks, you can use Azure backup to create backup jobs to protect your
data.
ØThis makes VM restores a snap.
ØCurrently Azure Backup supports disk sizes up to 32
tebibyte (TiB) disks.
Granular
access control
ØUsing Azure role-based access control, or RBAC, you
can specify granular access control for managed disks.
Øyou can assign specific permissions for managed disks
to your users.
Upload
your vhd
ØAzure managed disks make it easier to upload your
on-prem VMs to Azure because you can use direct upload to transfer your VHD
files to Azure managed disks.
ØYou can use direct upload to upload vhds up to 32 TiB
in size.
disk
roles in Azure
There are three
disk roles in Azure. These roles include data disks, OS disks, and temporary
disks.
ØData disk
ØOS disk
Øtemporary disk
Data
disk
ØA data disk is a managed disk that's attached to a
virtual machine to store application data, or other data you need to
keep.
ØWhen you attach a data disk to a VM, it's registered
as a SCSI drive.
ØYou can assign a drive letter to a data disk just like
any other physical disk in a physical server.
ØData disks have a max capacity of 32 terabytes, and
the number of data disks that you can attach to a virtual machine will be
determined by the size of the virtual machine itself.
OS
disk
ØEvery virtual machine has one attached operating
system disk. That OS disk has a pre-installed OS, which was selected when the
VM was created.
ØThis disk contains the boot volume.
ØThe max capacity of an OS disk is four terabytes.
Temporary
disk
ØMost VMs contain a temporary disk, which is not a
managed disk.
ØIt is associated with the virtual machine that will be
located in the underlying hardware from where the server is provisioned.
ØSo, the temporary disk will not be stored in a storage
account.
ØIt will be stored in the underlying hardware from
where this server is located.
In this
article we will learn about Azure Table storage account in azure.
•Azure Table storage is a service that stores non-relational structured
data (also known as structured NoSQL data) in the cloud.
•It provides a key/attribute store with a schema-less design.
•It means is that the data does not conform to a rigid schema.
it's easy to adapt your data as the needs of your
application evolve.
Access to Table storage data is fast and cost-effective
for many types of applications, and is typically lower in cost
Azure table storage, which is actually a NoSQL datastore,
often comes into play when an organization needs to store large amounts of
structured data. It’s perfect for scenarios that require the storage of
structured non-relational data.
Azure Table
storage usage
1.Organizations will often use table storage to
store flexible databases that include things like user data for Web
applications or maybe even address books or device information.
2.Table
storage allows you to store all kinds of entities in a table.
3.Storage accounts can contain as many tables
as you need up to the capacity limits of the storage account itself.
Table storage contains the following components:
Tables storage component diagram
URL format: Azure Table Storage
accounts use this format:
You can address Azure tables directly using this address
with the OData protocol
Accounts: All access to Azure
Storage is done through a storage account. For more information about storage
accounts.
All access to Azure Cosmos DB is done through a Table API
account. See Create a Table API account for details creating a Table API
account.
Table: A table is a collection of
entities. Tables don't enforce a schema on entities, which means a single table
can contain entities that have different sets of properties.
Entity: An entity is a set
of properties, similar to a database row. An entity in Azure Storage can be up
to 1MB in size. An entity in Azure Cosmos DB can be up to 2MB in size.
Properties: A property is a
name-value pair. Each entity can include up to 252 properties to store data.
Each entity also
has three system properties that specify a partition key, a row key,
and a timestamp.
Entities with the
same partition key can be queried more quickly, and inserted/updated in atomic
operations. An entity's row key is its unique identifier within a partition.
In this
article we will learn about Azure Queue storage account in azure.
ØAzure Queue Storage is a service for storing
large numbers of messages.
•Now these messages aren’t the type that you
would normally think of. We’re not talking about emails or anything like that.
Instead, these messages are used to facilitate communication between the
components of distributed applications.
•When using Azure queue storage, you can
access these messages from anywhere in the world through authenticated calls
via HTTP or HTTPS.Server message block
The Azure queue service is comprised of several
components. These include the URL format, a storage account, a queue, and
messages.
To access a queue, you must do so through a specific URL
format. The URL for a specific queue will include the storage account name and
the queue name.
Queue Storage contains the following components:
Diagram showing the relationship between a storage
account, queues, and messages.
URL format: Queues are
addressable using the following URL format:
Storage account: All
access to Azure Storage is done through a storage account. For information
about storage account capacity, see Scalability and performance targets for
standard storage accounts.
Queue: A queue contains a set of
messages. The queue name must be all lowercase. For information on naming
queues, see Naming queues and metadata.
Message: A message, in any
format, of up to 64 KB.
