Skip to main content

Task 01: Configure Azure Backup

Not part of the route at this time

This task is deferred. The toolkit does not run it, and its scripts are parked in scripts/deferred of azurelocal-toolkit as they were: they are not maintained and may not work. The page is kept for reference and will be rewritten when the task comes back.

Runbook Azure

DOCUMENT CATEGORY: Runbook
SCOPE: VM backup configuration with Azure Backup
PURPOSE: Deploy and configure Azure Backup for Azure Local VM protection
MASTER REFERENCE: Microsoft Learn - Back up Azure Local VMs with Azure Backup DESIGN REFERENCE: Azure Backup Appliance LLD

Status: Active

Azure Backup provides enterprise backup capabilities for Azure Local VMs with both local disk retention for fast recovery and Azure integration for offsite protection. This step covers Azure Backup deployment, agent installation, and protection group configuration.

Prerequisites​

RequirementDescriptionValidation
backup server VMDedicated VM on cluster with sufficient storage80 TB recommended for 800 VMs
Backup softwareA backup product that supports Azure Local (Azure Backup, Veeam, Commvault, Cohesity, Rubrik)Check the vendor support matrix for your Azure Local release
Recovery Services VaultAzure vault for online protectionCreated in Azure subscription
Network ConnectivityAzure Backup to Azure (443), Azure Backup to nodes (445, 135, dynamic RPC)Firewall rules configured
Cluster AccessDomain account with local admin on all nodesCredSSP or Kerberos delegation
Integration ComponentsSame version on guest VMs and hostsRequired for backup consistency

Values from infrastructure.yml​

The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.

Architecture Overview​

Azure Backup supports two backup approaches:

ApproachDescriptionUse Case
Host-level backupAgent on cluster nodes, backs up entire VMs at hypervisor levelFull VM recovery, OS-agnostic, no guest agent required
Guest-level backupAgent inside each VM, application-aware backupsSQL, Exchange, SharePoint item-level recovery
Azure Local Cloud Recommendation

Use both approaches: Host-level for full VM recovery and guest-level for critical application workloads requiring item-level recovery.

Hardware Specifications

For detailed hardware specifications, storage configuration, and appliance sizing, see the Azure Backup Appliance Low Level Design.

Key Storage Design: The BOSS card contains only OS (C:) and Azure Backup/SQL (E:) partitions. All staging (G:) and storage pool (S:) volumes must reside on RAID controller-attached drives.

Configuration Steps​

Step 1.1: Deploy backup server VM​

  1. Create a dedicated VM on the Azure Local cluster:
# Create Azure Backup VM
$VMName = "{{BACKUP_SERVER_NAME}}"
$VMPath = "{{CLUSTER_STORAGE_PATH}}\VMs"
$SwitchName = "{{MANAGEMENT_VIRTUAL_SWITCH}}"

New-VM -Name $VMName `
-MemoryStartupBytes 16GB `
-Generation 2 `
-Path $VMPath `
-SwitchName $SwitchName

# Configure VM resources
Set-VMProcessor -VMName $VMName -Count 8
Set-VMMemory -VMName $VMName -DynamicMemoryEnabled $false

# Add storage for Azure Backup disk pool (minimum 1.5x protected data size)
$StorageDisk = New-VHD -Path "$VMPath\$VMName\Storage.vhdx" -SizeBytes 10TB -Dynamic
Add-VMHardDiskDrive -VMName $VMName -Path $StorageDisk.Path
  1. Install Windows Server 2022 on the VM
  2. Join to domain and configure static IP
  3. Format storage disk for Azure Backup disk pool

Step 1.2: Install Azure Backup​

  1. Download the backup software for your chosen product. This task follows the Azure Backup based flow. Azure Backup, Veeam, Commvault, Cohesity, and Rubrik can all protect Azure Local VMs, so use your vendor installation guide if you chose another product. See Virtual machine resiliency for Azure Local.

  2. Run the installer and select required components:

  • SQL Server (bundled or use existing)
  • Backup server components
  1. Register with Recovery Services Vault:
  1. Navigate to Recovery Services vault → Properties → Backup Credentials
  2. Click Download to get vault credentials file
  3. Copy to backup server
  4. During Azure Backup setup, specify the vault credentials file

Step 1.3: Configure Azure Backup Storage Pool​

  1. Open Azure Backup Administrator Console
  2. Navigate to Management → Disk Storage
  3. Click Add to add storage disks
  4. Select the storage disk attached to Azure Backup VM
  5. Configure storage allocation:
RecommendationSize Formula
Replica volumeProtected data size × 2
Recovery point volumeProtected data size × retention days × daily change rate

Step 1.4: Install Protection Agent on Cluster Nodes​

Application Control

If Azure Benefits is enabled with WDAC, temporarily switch to Audit mode before agent installation.

PowerShell​

When to use: This task is parked and nothing runs it. The scripts below are under scripts/deferred and they still read an older configuration layout.

Script​

ScriptWhat it does
scripts/deferred/backup-dr/phase-03-backup-dr/task-01-configure-azure-backup/azurecli/Set-BackupConfiguration.azcli.ps1Configures Azure Backup for Azure Local cluster using Azure CLI.
scripts/deferred/backup-dr/phase-03-backup-dr/task-01-configure-azure-backup/powershell/Set-BackupConfiguration.ps1Configures Azure Backup and Disaster Recovery for Azure Local.

Run​

.\Set-BackupConfiguration.azcli.ps1 -ClusterName "AZL-CLUSTER01" -ResourceGroupName "rg-azl-backup" -VaultName "rsv-azl-prod"

.\Set-BackupConfiguration.ps1 -ClusterName "azl-cluster-01" -ResourceGroup "rg-azl-01" -VaultName "rsv-azl-01"

After agent installation, re-enable WDAC if it was disabled.

Step 1.5: Create Protection Group for VMs​

  1. In backup console, select Protection → Create protection group

  2. Select protection type: Servers

  3. Select group members:

  • Highly Available VMs: Select from cluster for clustered VMs
  • Hyper-V (Unmanaged) VMs: Select from individual nodes
  1. Configure Data Protection Method:
  • Name: {{PROTECTION_GROUP_NAME}}
  • Enable: I want short-term protection using Disk
  • Enable: I want online protection (for Azure backup)
  1. Configure Short-Term Goals:
  • Retention range: {{BACKUP_RETENTION_DAYS}} days
  • Synchronization frequency: Every 15 minutes or before recovery point
  1. Configure Disk Allocation:
  • Review and accept default allocations
  • Enable Automatically grow the volumes if needed
  1. Configure Online Protection:
  • Select data for online protection
  • Configure online backup schedule (daily/weekly)
  • Set online retention policy (up to 99 years)
  1. Review and create protection group

Step 1.6: Configure Backup Schedules​

Example protection schedule:

Schedule TypeFrequencyTimeRetention
Express full backupDaily9:00 PM14 days (disk)
Online backupDaily11:00 PM30 days (Azure)
Weekly fullSunday2:00 AM5 weeks (Azure)
Monthly1st Sunday2:00 AM12 months (Azure)
# Example: Modify protection group schedule via PowerShell
$pg = Get-DPMProtectionGroup -DPMServerName "{{BACKUP_SERVER_NAME}}" |
Where-Object { $_.FriendlyName -eq "{{PROTECTION_GROUP_NAME}}" }

# Set synchronization schedule
$sched = Get-DPMPolicySchedule -ProtectionGroup $pg -ShortTerm

# Modify as needed and commit
Set-DPMPolicySchedule -ProtectionGroup $pg -Schedule $sched

Validation​

Verify Agent Status​

# On backup server - check agent status
Get-DPMProductionServer -DPMServerName "{{BACKUP_SERVER_NAME}}" |
Select-Object Name, ServerProtectionState, AgentVersion

Expected output shows all cluster nodes with Valid protection state.

Run Test Backup​

  1. In backup console, select a protected VM
  2. Right-click → Create recovery point
  3. Select Online protection to test Azure connectivity
  4. Monitor job in Monitoring → Jobs

Verify Azure Recovery Points​

  1. Navigate to Recovery Services vault → Backup items
  2. Select the backup management type for your product
  3. Verify VMs appear with recent recovery points

Validation Checklist​

ComponentVerificationExpected Result
Backup serviceBackup product service on the backup serverRunning
Protection AgentAgent status in consoleValid on all nodes
Protection GroupGroup statusOK, no warnings
Disk Recovery PointsLatest recovery pointWithin last 24 hours
Online Recovery PointsAzure portal checkSynced to Azure

Recovery Procedures​

Recover Entire VM (Host-Level)​

  1. Navigate to Recovery → Select date with recovery point
  2. Expand server → Select VM
  3. Right-click → Recover
  4. Select recovery type:
  • Recover to original instance: Replaces existing VM
  • Recover as virtual machine to any host: New location
  • Copy to a network folder: Export VHD files

Recover Files (Item-Level Recovery)​

Hyper-V Role Required

Item-level recovery requires Hyper-V role on backup server.

  1. Select VM recovery point
  2. Right-click → Recover
  3. Select Copy to a network folder
  4. Browse recovered VHD and extract files

Cross-Cluster Recovery​

When restoring a VM to a different cluster:

  1. Recover VM to alternate location
  2. VM will be unmanaged (not Arc-connected)
  3. Re-register with Azure Arc:

Register-AzStackHCI -SubscriptionId "{{AZURE_SUBSCRIPTION_ID}}" `
-ResourceGroupName "{{AZURE_RESOURCE_GROUP}}" `
-ArcServerResourceGroupName "{{ARC_RESOURCE_GROUP}}"
45-Day Window

If restoring to the same cluster, Azure Arc connection is maintained automatically if within the 45-day reconnection window.

Troubleshooting​

SymptomLikely CauseResolution
Agent installation failsWDAC blockingSwitch to Audit mode, install, then re-enable
WMI query timeoutFirewall blockingDisable AzsHci-ImdsAttestation-Block-TCP-In
Backup fails for HA VMsCluster not selectedSelect VMs from cluster node, not individual hosts
Online backup slowBandwidth limitedConfigure throttling in Azure Backup or schedule off-hours
Recovery point missingReplica invalidRun consistency check on protection group

Capacity Planning​

Protected DataAzure Backup Disk StorageAzure Storage
10 TB30 TBVaries by retention
50 TB150 TBVaries by retention
100 TB300 TBVaries by retention
Storage Formula

Azure Backup storage = (Protected data × 2) + (Protected data × retention days × daily change rate)

Variables Reference​

VariableDescriptionExample
{{BACKUP_SERVER_NAME}}backup server hostnamebkp-dal-01
{{PROTECTION_GROUP_NAME}}Protection group nameAzureLocal-VMs-Prod
{{RECOVERY_VAULT_NAME}}Recovery Services vault namersv-azl-dal-prod-01
{{BACKUP_RETENTION_DAYS}}Local disk retention days14

Next Steps​

After configuring Azure Backup:

  1. ➡️ Task 2: Configure Site Recovery — Set up VM replication to Azure
  2. Document protection group assignments
  3. Configure email notifications for backup failures
  4. Schedule regular restore tests

Toolkit Reference

Scripts for this task are located in the azurelocal-toolkit repository under scripts/deploy/ in the appropriate task folder.


Alternatives​

The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.

PreviousUpNext
---Phase 03: Backup & DRTask 02: Configure Site Recovery ->

Version Control​

VersionDateAuthorChanges
1.0.02025-03-25Azure Local CloudInitial release