Implement and manage storage in Azure Flashcards
Azure Storage
Azure Blobs,
Azure Files,
Azure Queues
Azure Tables
What is a storage account?
A storage account is a container that groups a set of Azure Storage services together. Only data services from Azure Storage can be included in a storage account (Azure Blobs, Azure Files, Azure Queues, and Azure Tables)
storage accounts expanded
A storage account is an Azure resource and is included in a resource group. The following illustration shows an Azure subscription containing multiple resource groups, where each group contains one or more storage accounts
Storage account settings
A storage account defines a policy that applies to all the storage services in the account. For example, you could specify that all the contained services will be stored in the West US datacenter, accessible only over https, and billed to the sales department’s subscription
The settings that are controlled by a storage account are
Subscription
Location
Performance
Standard allows you to have any data service (Blob, File, Queue, Table) and uses magnetic disk drives. Premium introduces additional services for storing data
replication / storage
Determines the strategy used to make copies of your data to protect against hardware failure or natural disaster. At a minimum, Azure will automatically maintain three copies of your data within the data center associated with the storage account. This is called locally-redundant storage (LRS), and guards against hardware failure but does not protect you from an event that incapacitates the entire datacenter. You can upgrade to one of the other options such as geo-redundant storage (GRS) to get replication at different datacenters across the world
Access tier
Controls how quickly you will be able to access the blobs in this storage account. Hot gives quicker access than Cool, but at increased cost. This applies only to blobs, and serves as the default value for new blobs
Secure transfer required
A security feature that determines the supported protocols for access. Enabled requires HTTPs, while disabled allows HTTP
Virtual networks
Virtual networks: A security feature that allows inbound access requests only from the virtual network(s) you specify
grs vs lrs
Geo-redundant storage costs more than locally-redundant storage. Premium performance and the Hot access tier increase the cost of blobs
Choose your account settings
The storage account settings we’ve already covered apply to the data services in the account. Here, we will discuss the three settings that apply to the account itself, rather than to the data stored in the account:
Name
Each storage account has a name. The name must be globally unique within Azure, use only lowercase letters and digits and be between 3 and 24 characters.
Deployment model
A deployment model is the system Azure uses to organize your resources. The model defines the API that you use to create, configure, and manage those resources. Azure provides two deployment models
Deployment model c
Resource Manager: the current model that uses the Azure Resource Manager API
Classic: a legacy offering that uses the Azure Service Management API
Account kind
StorageV2 (general purpose v2): the current offering that supports all storage types and all of the latest features
Recommended
Storage (general purpose v1): a legacy kind that supports all storage types but may not support all features
Blob storage: a legacy kind that allows only block blobs and append blobs
gpv2 + resource manager
The core advice here is to choose the Resource Manager deployment model and the StorageV2 (general purpose v2) account kind for all your storage accounts. The other options still exist primarily to allow existing resources to continue operation. For new resources, there are few reasons to consider the other choices
Disk roles
OS disk. One disk in each virtual machine contains the operating system files. When you create a virtual machine, you select a virtual machine image and that fixes the operating system and the OS disk that’s attached to the new machine. The OS disk has a maximum capacity of 2,048 GB
Disk roles 2
Data disk. You can add one or more data virtual disks to each virtual machine to store data. For example, database files, website static content, or custom application code should be stored on data disks. The number of data disks you can add depends on the virtual machine size. Each data disk has a maximum capacity of 32,767 GB
Disk roles 3
Temporary disk. Each virtual machine contains a single temporary disk, which is used for short-term storage applications such as page files and swap files. The contents of temporary disks are lost during maintenance events, so don’t use these disks for critical data. These disks are local to the server and aren’t stored in a storage account
Ephemeral OS disks
An ephemeral OS disk is a virtual disk that saves data on the local virtual machine storage
An ephemeral disk has faster read-and-write latency than a managed disk. It’s also faster to reset the image to the original boot state if you’re using an ephemeral disk. However, an individual virtual machine failure might destroy all the data on an ephemeral disk and leave the virtual machine unable to boot. Because ephemeral disks reside locally to the host, they incur no storage costs and are free
Managed disks
A managed disk is a virtual hard disk for which Azure manages all the required physical infrastructure. Because Azure takes care of the underlying complexity, managed disks are easy to use. You can just provision them and attach them to virtual machines
Virtual hard
are stored as page blobs in an Azure Storage account, but you don’t have to create storage accounts, blob containers, and page blobs yourself or maintain this infrastructure later
Benefits
Simple scalability
Simple scalability. You can create up to 50,000 managed disks of each type in each region in your subscription
High availability
Managed disks support 99.999% availability by storing data three times. If there’s a failure in one replica, the other two can maintain full read-write functionality
Integration with availability sets and zones
If you place your virtual machines into an availability set, Azure automatically distributes the managed disks for those machines into different fault domains so that your machines are resilient to localized failures. You can also use availability zones, which distribute data across multiple datacenters, for even greater availability
Support for Azure Backup
Azure Backup natively supports managed disks, which includes encrypted disks
Granular access control
You can use Azure role-based access control (RBAC) to grant access to specific user accounts for specific operations on a managed disk. For example, you could ensure that only an administrator can delete a disk
Support for encryption
To protect sensitive data on a managed disk from unauthorized access, you can encrypt it by using Azure Storage Service Encryption (SSE), which is provided with Azure Storage accounts. Alternatively, you can use Azure Disk Encryption (ADE), which uses BitLocker for Windows virtual machines, and DM-Crypt for Linux virtual machines.
Input/output operations per second (IOPS)
IOPS measure the rate at which the disk can complete a mix of read and write operations. Higher performance disks have higher IOPS values
Throughput
Throughput measures the rate at which data can be moved onto the disk from the host computer and off the disk to the host computer. Throughput is also called data transfer rate and is measured in megabytes per second (MBps). Higher performance disks have higher throughput
Ultra SSD
Ultra SSDs provide the highest disk performance available in Azure. Choose them when you need the fastest storage performance, which includes high throughput, high IOPS, and low latency.
Ultra disks can have capacities from 4 GB up to 64 TB
Ultra SSD LIMITS
They’re only available in a subset of Azure regions.
They can only be attached to virtual machines that are in availability zones.
They can only be attached to ES/DS v3 virtual machines.
They can only be used as data disks and can only be created as empty disks.
They don’t support disk snapshots, virtual machine images, scale sets, Azure Disk Encryption, Azure Backup, or Azure Site Recovery
Premium SSD
Premium SSDs are the next tier down from ultra disks in terms of performance, but they still provide high throughput and IOPS with low latency. Premium disks don’t have the current limitations of ultra disks. For example, they’re available in all regions and can be used with virtual machines that are outside of availability zones.
You can’t adjust performance without detaching these disks from their virtual machine. Also, you can only use premium SSDs with larger virtual machine sizes, which are compatible with premium storage.
Standard SSD
Standard SSDs in Azure are a cost-effective storage option for virtual machines that need consistent performance at lower speeds. Standard SSDs aren’t as fast as premium or ultra SSDs, but they still have latencies in the range of 1 millisecond to 10 milliseconds and up to 6,000 IOPS. They’re available to attach to any virtual machine, no matter what size it is.
Standard HDD
If you choose to use standard HDDs, data is stored on conventional magnetic disk drives with moving spindles. Disks are slower and speeds are more variable than for SSDs, but latencies are under 10 ms for write operations and 20 ms for reads. As for standard SSDs, you can use standard HDDs for any virtual machine.
Locally redundant storage
Locally redundant storage (LRS) copies your data three times across separate racks of hardware in a datacenter, inside one region. Even if there’s a hardware failure, or if maintenance work is happening in the datacenter, this replication type ensures data is available for use.
LRS doesn’t protect you from a datacenter-wide outage. If the datacenter goes down, you could lose your data
Geographically redundant storage
With geographically redundant storage (GRS), your data is copied three times within one region, and three times in a secondary region that’s paired with it. This way, if your primary region is experiencing an outage, your secondary region is available for use