Azure VM Selective Disk Backup

Hey Folks

Recently Microsoft has announched that, Azure now supports VM Selective backups.

What is this selective backup??. This will allow the admins/customers to backup only the selected disks in a VM to Azure backup. But at the moment we can only perform the following scnearios

Example

We have a Linux VM which has OS Disk and 2 data disks as mention below

What we can do is

Backup All Data disks (Typical option)
Backup only the OS disk
Backup OS Disk + Disk 1
Backup OS Disk + Disk 2

What we cannot do is back up on the data disks without the OS disk.

I will talk about option 2 and 3 ( 4 is same as 3). Basically I will be covering the new options. Alos on this to note, at the moment option 3 only can be set from powershell. There is no GUI option for it.

Backup OS Disk + Data Disk 1

Get VM Disk Details

Get-AzDisk -ResourceGroupName AE-DEV-LINUX

Get Azure VM Datadisk details

$Vm = Get-AzVM -ResourceGroupName AE-DEV-LINUX -Name LinuxVm01

Determine Datadisk lun details

$vm.StorageProfile.DataDisks

Specify the data disk lun numbers seperated with a comma

$disks = ("0")
$targetVault = Get-AzRecoveryServicesVault -ResourceGroupName AE-DEV-LINUX -Name LinuxRecovery

Setting the vault content

Set-AzRecoveryServicesVaultContext -Vault $targetVault

GetBackup policy details to a variable

$pol = Get-AzRecoveryServicesBackupProtectionPolicy -Name "Linux"

Enable Protection

Enable-AzRecoveryServicesBackupProtection -Policy $pol -Name "LinuxVm01" -ResourceGroupName "AE-DEV-LINUX" -InclusionDisksList $disks -VaultId $targetVault.ID

check the Backup status

$item= Get-AzRecoveryServicesBackupItem -BackupManagementType "AzureVM" -WorkloadType "AzureVM" -VaultId $targetVault.ID -FriendlyName "LinuxVm01"

Backup OS Disk Only

To backup the OS disk only, we can achive this from GUi. Simply browse torecovery services vault.

Once you select the VM, you can simply tick the option to backup OS only

Or what you can do is powershell use the below parameer to exclude all data disks

Hope this helps someone (y)

Comments

Deploying an Automation Account with a Runbook and Schedule Using Bicep

Introduction Automation is a key component in many organizations' cloud strategy. Azure Automation allows you to automate the creation, deployment, and management of resources in your Azure environment. In this post, we will walk through the process of deploying an Automation Account with a Runbook and Schedule using Bicep, a new domain-specific language for deploying Azure resources. Intention My intention at the end is to run a PowerShell script to start and shutdown Azure VMs based on tag values. PowerShell script that I have used is from below l ink. And two of me collogue s ( Michael Turnley and Saudh Mohomad helped to modify the PowerShell script. Prerequisites Before we begin, you will need the following: An Azure subscription The Azure CLI installed on your machine. The Azure Bicep extension for the Azure CLI Creating the Automation Account The first step in deploying an Automation Account with a Runbook and Schedule is to create the Aut

Updating Azure VM Data Disk Sizes

Summary Hope you are doing great, this time I came up with a simple azure DevOps solution for updating VM disk sizes. The current project that I'm in has a bunch of virtual machines. So, we need a way to update the VM disk with minimal administrative effort and changes. In this scenario, we have used Bicep as the IAC language Azure DevOps pipelines YAML variable files Here is the high-level workflow for a particular VM in the solution YAML Pipeline file got two workflows, firstly the VM build pipeline, and the second is the disk update one. If you focus on the green arrow and the purple arrow, basically I'm modifying the same bicep module file and passing the same set of variables. You may wonder why we cannot use the same flow to build the VM and update the disk later, that's because for the disk updates VM needs to be in a shutdown state, and other components in the 1st flow need the VM up and running especially the extension modules YAML Variable Files I have decided t

Securing Azure Services with Fetian FIDO

Hey Folks Here again with another security topic with Fetian Fido. And once again Fetian devices proved their excellent quality and stability. For this I choose Fetian K33 - AllinPass FIDO Security Key – FEITIAN (ftsafe.com) and K39 - Single-button FIDO Security Keys | FEITIAN (ftsafe.com) Use case In an organization following changes needs to be implemented. 1. Update the password policy 2. Update the user session time out to 30 minutes Once these changes being implemented, the following issues need to be addressed 1. Users' complaint new passwords need to be so long 2. Users complain sessions time out makes them work so much slower with the longer passwords 3. Etc... Solution One of my friends reached out to me to help solve this problem. All I could think of was using passwordless auth with FIDO devices. We have decided to use Fido2 keys for better security and flexibility for the users. The FIDO (Fast IDentity Online) Alliance helps to promote open authentication stand

Azure with Danidu

Search This Blog