Lesson: Azure Managed Disks Design

Introduction: What are Azure Managed Disks?

In the realm of cloud infrastructure, storage is the foundation upon which your applications run. Azure Managed Disks are block-level storage volumes that are managed by Azure and used with Azure Virtual Machines (VMs).

Unlike "unmanaged disks," where you are responsible for managing the storage accounts that hold the disk files (VHDs), Azure Managed Disks handle the underlying storage account management for you. When you create a managed disk, Azure automatically manages the storage resources, ensuring high availability, scalability, and performance without requiring you to worry about storage account limits or IOPS throttling at the account level.

Why use Managed Disks?

• Simplified Management: No need to manage storage accounts or VHD files.
• Improved Reliability: Azure automatically distributes disks into storage scale units to prevent single points of failure.
• Scalability: You can easily scale your storage performance and capacity up or down.
• Security: Support for Azure Disk Encryption (ADE) and Server-Side Encryption (SSE) with Customer-Managed Keys (CMK).

Understanding Disk Types and Tiers

Choosing the right disk is a balance between IOPS (Input/Output Operations Per Second), Throughput (MB/s), and Cost.

1. Ultra Disk

The highest-performing storage option. Designed for data-intensive workloads like SAP HANA, top-tier databases, and transaction-heavy workloads.

• Key feature: You can dynamically change the performance (IOPS/Throughput) of the disk without restarting the VM.

2. Premium SSD v2

The newest high-performance offering, providing a better price-to-performance ratio than the original Premium SSD for most general-purpose enterprise workloads.

3. Premium SSD

Designed for production and performance-sensitive workloads. It provides consistent high performance and low latency.

4. Standard SSD

Best for web servers, lightly used enterprise applications, and dev/test environments. It provides more consistent performance than Standard HDD.

5. Standard HDD

The most cost-effective option. Best for backup, non-critical, or infrequent access workloads.

Practical Implementation

When designing your storage solution, you often define these resources using Infrastructure as Code (IaC). Below is an example using Azure CLI to create a VM with a Premium SSD.

Example: Creating a Managed Disk via Azure CLI

# Create a resource group
az group create --name MyResourceGroup --location eastus

# Create a VM with a Premium SSD OS disk
az vm create \
  --resource-group MyResourceGroup \
  --name MyVM \
  --image Ubuntu2204 \
  --admin-username azureuser \
  --generate-ssh-keys \
  --os-disk-sku Premium_LRS

Example: Attaching a Data Disk

If you need additional storage for your application data (e.g., a SQL database folder), you create a data disk and attach it to the VM:

# Create a 128GB Premium SSD data disk
az disk create \
  --resource-group MyResourceGroup \
  --name MyDataDisk \
  --size-gb 128 \
  --sku Premium_LRS

# Attach the disk to the existing VM
az vm disk attach \
  --resource-group MyResourceGroup \
  --vm-name MyVM \
  --name MyDataDisk

Note: After attaching a disk, you must log into the VM’s operating system to initialize, format, and mount the disk before it becomes usable.

Best Practices for Design

1. Right-Size Your Disks: Do not over-provision. You pay for the capacity allocated, even if it is not used. Use Azure Advisor to identify underutilized disks.
2. Separate OS and Data Disks: Always place your OS on the OS disk and your application data/logs on separate data disks. This prevents OS issues from impacting data integrity and allows for easier snapshots.
3. Use Performance Tiers: Only use Ultra or Premium SSDs for workloads that truly require sub-millisecond latency. For general file storage, use Standard SSD or HDD.
4. Implement Snapshots: Use Azure Disk Snapshots for point-in-time backups. Automate this using Azure Backup to ensure compliance and disaster recovery readiness.
5. Enable Encryption: Always enable encryption at rest. Azure provides Platform-Managed Keys by default, but for high-security environments, use Customer-Managed Keys (CMK) via Azure Key Vault.

Common Pitfalls

• Ignoring IOPS Limits: Every VM size has a maximum IOPS and throughput limit. Attaching a high-performance disk to a small VM size will result in the VM "throttling" the disk performance. Always check the VM size documentation for disk limits.
• Forgetting to Format: A common "gotcha" for beginners is attaching a disk and wondering why it doesn't appear in the file system. Remember that Azure provides the "block device," but the OS must create the file system (NTFS/XFS/EXT4).
• Mixing Storage Tiers Incorrectly: Placing the OS disk on a slow tier (Standard HDD) while expecting high application performance is a recipe for a sluggish user experience.

💡 Pro-Tip: Bursting

Premium SSDs and Standard SSDs support Disk Bursting. This allows your disk to exceed its provisioned performance for short periods (up to 30 minutes) to handle unexpected traffic spikes without needing to permanently upgrade the disk tier.

Key Takeaways

• Managed Disks abstract the complexity of storage account management, offering high availability and ease of use.
• Selection matters: Match your disk type (Ultra, Premium, Standard) to the specific IOPS and latency requirements of your application.
• Design for Scale: Always check the VM's IOPS/Throughput limits to ensure the VM can handle the disk's potential performance.
• Automation: Use Infrastructure as Code (ARM templates, Bicep, or Terraform) to ensure consistent disk configurations across environments.
• Security: Leverage encryption at rest and automated snapshot policies to protect your data integrity and availability.