Study guide

5.6 Backup, Restore, and Operational Maintenance for VMs

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

5.6 Backup, Restore, and Operational Maintenance for VMs

Key Takeaways Explain This Topic AI

Azure Backup protects VMs through vaults, policies, recovery points, and restore workflows; snapshots alone are not a full backup strategy.

Operational maintenance includes patching, monitoring, update assessment, boot diagnostics, serial console, run command, redeploy, and change control.

Restore choices include creating a new VM, restoring disks, replacing disks in some scenarios, and file-level recovery.

Backup failures commonly involve agent health, policy scope, vault configuration, locks, soft delete, network restrictions, and unsupported VM states.

Last updated: May 2026

Backup Architecture

Azure Backup for VMs is usually configured through a Recovery Services vault. The vault stores backup metadata and recovery points according to a backup policy. A policy defines schedule, frequency, retention, and backup behavior. The protected item is the VM. Recovery points can be crash-consistent, file-system consistent, or application-consistent depending on OS, agents, and workload support.

A snapshot is not the same as Azure Backup. Snapshots are useful for short-term disk capture and pre-change rollback, but a vault policy gives centralized retention, restore workflows, soft delete, monitoring, alerts, and operational reporting. In exam scenarios, choose snapshots for quick disk point-in-time copy and Azure Backup for managed recovery and retention.

  • Component Role Administrator task
  • Recovery Services vault Backup management container Create in proper region and configure security
  • Backup policy Schedule and retention Match RPO and retention requirements
  • Protected item VM under backup Enable, monitor, and troubleshoot protection
  • Recovery point Restore source Select correct date and consistency type
  • Soft delete Protection against accidental deletion Understand retention and undelete behavior

Portal path: Recovery Services vaults > vault name > Backup > Azure Virtual Machine. You can also enable backup during VM creation on the Management tab. For production, confirm the vault region, redundancy, soft delete, immutability if required, and access controls.

  • CLI example: az backup vault create \
  • -resource-group rg-prod-ops \
  • -name rsv-prod-eastus \
  • -location eastus
  • az backup protection enable-for-vm \
  • -resource-group rg-prod-ops \
  • -vault-name rsv-prod-eastus \

--vm /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-prod-compute/providers/Microsoft.Compute/virtualMachines/vm-app-01 \

  • -policy-name DefaultPolicy
  • az backup job list -g rg-prod-ops --vault-name rsv-prod-eastus --output table
  • Restore Options

Restore method depends on the failure. If a user deleted files, file-level recovery may be enough. If the OS disk is corrupted, restoring disks or replacing the OS disk may be appropriate. If the VM is lost or you want isolated validation, create a new VM from a recovery point. If the region is unavailable, you need a cross-region or disaster recovery design that was planned before the outage.

  • Problem Restore choice Notes
  • Accidental file deletion File recovery Mount recovery point and copy files
  • Bad application update Restore disks or new VM Validate app consistency
  • OS boot failure Restore OS disk or create new VM Keep original for investigation if needed
  • VM deleted Restore VM or disks Depends on backup state and retained points
  • Regional disaster ASR failover or cross-region restore where configured Must be planned and tested

Do not restore over production without a rollback plan. A restored VM can conflict with names, IPs, domain membership, or application identity. Restoring disks gives more control but requires you to attach them correctly and repair boot or data configuration.

Maintenance Operations

Operational maintenance includes planned patching, guest configuration, monitoring, performance review, security posture, backup verification, and cost controls. Azure Update Manager can assess and orchestrate updates for Azure VMs and hybrid servers through Azure Arc. Maintenance configurations can help control platform maintenance timing for supported resources. Auto-shutdown can reduce cost for dev/test but should not be used for production workloads unless intentional.

  • Common commands: az vm get-instance-view -g rg-prod-compute -n vm-app-01 --query instanceView.statuses
  • az vm boot-diagnostics get-boot-log -g rg-prod-compute -n vm-app-01

az vm repair create -g rg-prod-compute -n vm-app-01 --repair-username repairadmin --repair-password 'Use-A-Secure-Method'

  • az vm redeploy -g rg-prod-compute -n vm-app-01
  • az vm reapply -g rg-prod-compute -n vm-app-01

Redeploy moves the VM to another host and can resolve host issues. Reapply reapplies the VM model and can help when the platform state is inconsistent. VM repair commands can create a repair VM and attach a copy of the OS disk for offline repair in supported workflows. Run Command can execute scripts when normal access is unavailable but the VM agent is working.

Monitoring and Diagnostics

For VM health, combine platform metrics, guest metrics, logs, boot diagnostics, and alerts. Azure Monitor can collect VM metrics and logs through the Azure Monitor Agent and data collection rules. VM insights provides performance and dependency views. Boot diagnostics captures screenshots and serial logs that are useful when the VM fails before network services start.

  • Signal Use it for
  • Activity log Control plane operations such as start, resize, redeploy
  • Metrics CPU, disk, network, availability signals
  • Guest logs OS and application troubleshooting
  • Boot diagnostics Boot failure, kernel panic, blue screen, login prompt evidence
  • Serial console Emergency command-line access for supported VMs
  • Backup jobs Protection success, duration, and failures
  • Backup Troubleshooting

Scenario 1: Backup fails with extension or snapshot errors. Check VM agent status, extension health, guest OS state, disk status, and whether another backup or snapshot operation is already running. For Windows application consistency, VSS issues inside the guest can matter.

Scenario 2: Backup cannot be enabled. Check whether the VM and vault are in supported regions, RBAC permissions, locks, policy restrictions, and whether the VM is already protected by another vault in a conflicting way. Confirm the selected backup policy is valid.

Scenario 3: Restore completes but application fails. Check restored IP addressing, DNS, certificates, managed identity permissions, secrets, domain trust, firewall rules, and database connection strings. Infrastructure restore does not guarantee application consistency if the app needs coordinated recovery steps.

Scenario 4: A user deletes a protected VM and asks for immediate deletion of backup data. Soft delete and security settings may intentionally retain backup data for a period to protect against accidental or malicious deletion. The exam may ask which feature prevents immediate permanent loss of backup items.

Operational Runbook Pattern

For a production VM, define a runbook that includes owner, business service, RPO, RTO, backup policy, patch window, monitoring alerts, escalation path, access method, recovery test schedule, and rebuild method. Infrastructure as code should define the VM and baseline settings. Backup and monitoring should be verified after deployment, not assumed.

Before risky maintenance, confirm the latest successful backup, create a short-lived snapshot if appropriate, review change windows, drain load-balanced traffic, apply updates to one instance first, validate health probes and application tests, then continue. For scale sets, prefer rolling upgrades and health checks. For single VMs, plan downtime and rollback.

AZ-104 does not require deep application administration, but it does require administrator judgment. Know when to use backup, when to use snapshots, when to redeploy, when to use serial console, and when the problem is actually DNS, NSG, guest firewall, or application configuration.