Scribd
Upload
8 views3 pages

Azure 23

The document outlines the reasons for moving Azure VMs, such as reducing latency by relocating to a closer region or increasing availability through availability zones. It details the types of Azure managed disks available for different workloads, key management tasks, and tools for managing these disks. Additionally, it covers Azure Disk Encryption for securing data and the process for moving VMs between resource groups using the Azure Portal.

Uploaded by

Mahmud Rayhan Shajib
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
8 views3 pages

Azure 23

The document outlines the reasons for moving Azure VMs, such as reducing latency by relocating to a closer region or increasing availability through availability zones. It details the types of Azure managed disks available for different workloads, key management tasks, and tools for managing these disks. Additionally, it covers Azure Disk Encryption for securing data and the process for moving VMs between resource groups using the Azure Portal.

Uploaded by

Mahmud Rayhan Shajib
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

Reasons to move Azure VMs

Azure VM is already deployed in one region and a new region support is added that is closer to
the end users of your application or service. In this scenario,
An Azure Virtual Machine is already deployed in the region and one more new region support is
added which is closer to end users of the applications or services.
Let’s assume a scenario as follows:
● You want to move your VMs to a new region to reduce latency. Use the same procedure if
you want to consolidate memberships or have governance or organization rules you need to
move.
● Your VM is deployed as a single-instance VM or as part of an availability set. If you want to
increase the availability of SLAs, you can move your VMs into an availability zone.
--Back to Index-- 69
Azure-managed disk types
Managing virtual machine disks in Azure involves several key tasks, including creating,
attaching, resizing, and managing the performance of disks. Here are some important
aspects to consider:
Types of Azure Managed Disks
Azure offers several types of managed disks, each suited for different workloads:
● Ultra Disks: High-performance, low-latency disks ideal for data-intensive
applications.
● Premium SSDs: Suitable for production workloads requiring high IOPS and low
latency.
● Standard SSDs: Cost-effective storage for less critical workloads.
● Standard HDDs: Best for backup and non-critical data.
Key Management Tasks
1. Creating and Attaching Disks:
○ You can create and attach data disks to your VMs using the Azure portal, Azure
CLI, or Azure PowerShell
○ After attaching, you need to initialize and format the disk within the VM.
2. Resizing Disks:
○ Disks can be resized to accommodate growing data needs. This can be done
without downtime
3. Snapshots and Backup:
○ Snapshots provide a point-in-time backup of your disks. They can be used to
restore data or create new disks.
○ Azure Backup can automate the backup process for managed disks.
4. Performance Management:
○ Choose the right disk type based on your workload requirements to ensure
optimal performance.
○ Monitor disk performance and adjust configurations as needed.
--Back to Index-- 70
Source: Select a disk type for Azure IaaS VMs - managed disks
Tools for Management
● Azure Portal: Provides a graphical interface for managing disks.
● Azure CLI and PowerShell: Offer command-line tools for scripting and
automation.
● Azure Storage Explorer: A tool for managing disks, including uploading and
downloading VHDs.
Manage virtual machine disks
1. Azure Portal
● Create a New Disk:
1. Navigate to the Azure portal.
2. Search for and select "Disks."
3. Click "Create disk."
4. Specify the disk name, size, location, and type.
5. Click "Create."
● Attach a Disk to a VM:
1. Navigate to the VM's overview page.
2. Click "Disks."
3. Click "Create and attach a new disk."
4. Select the desired disk from the list or create a new one.
5. Specify the LUN (Logical Unit Number) for the disk.
6. Click "OK."
--Back to Index-- 71
● Detach a Disk from a VM:
1. Navigate to the VM's overview page.
2. Click "Disks."
3. Select the disk to be detached.
4. Click "Detach."
Azure Disk Encryption(ADE) for Windows Virtual
Machines(VMs)
Azure Disk Encryption helps protect and secure your data while meeting your
organizational
security and compliance commitments. It uses Windows' BitLocker feature to
provide volume
encryption for OS and data disks of Azure virtual machines (VMs) and
integrates with Azure Key
Vault to help you control and manage disk encryption keys and secrets.
ADE is Zone resilient, similar to VMs. FYI→Azure Services that support
Availability Zones.
If you use Microsoft Defender for Cloud, you'll get a warning if you have
unencrypted VMs.
Warnings are shown as high severity and it is recommended to encrypt these
VMs.
Supported VMs for ADE : Generations 1 & Generation 2 VMs and also VMs
with premium
storage.
ADE is not available on Basic, A-series VMs, or on virtual machines with less
than 2 GB of
memory.
Supported operating systems are
➔ Windows client : Windows 8 and later,
➔ Windows Server: Windows Server 2008 R2 and later,
➔ Windows 10 Enterprise multi-session and later.
Requirements: Networking, Group Policy, and Encryption key storage
requirements
Move VMs from one resource group to another
You can move a VM from one resource group to another one with Portal, CLI,
and powershell.
Ex: Using Azure Portal
1. Go to the Azure portal to manage the resource group containing the VM to
move.
Search for and select Resource groups.
2. Choose the resource group containing the VM that you would like to move.
3. At the top of the page for the resource group, select Move and then select
Move to another
resource group. The Move resources page opens.
4. Select each of the resources to move. In most cases, you should move all
of the related
resources that are listed.
5. Select an existing resource group or enter a name to create a new
resource group.
6. When you're done, select that you understand that new resource IDs will
be created and
that the new IDs will need to be used with the VM after the move, and then
select OK.
You can practice this using with our Azure Cloud Sandbox Environment

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy