Restoring Linux virtual machines (VMs) in Microsoft Azure can be daunting for IT teams especially with the nuances between Gen1 and Gen2 VM types. Veeam Backup for Microsoft Azure simplifies this process, offering a reliable and efficient solution for restoring both VM generations. In this guide, we’ll walk through the step‑by‑step process, highlight key considerations, and share best practices to ensure a smooth and successful restoration.
Understanding Gen1 vs Gen2 Azure Linux VMs
What are Gen1 and Gen2 VMs?
Visual differences are subtle, but the underlying architecture varies significantly:
- Gen1 VMs rely on BIOS and MBR, with a simpler boot environment.
- Gen2 VMs use UEFI and GPT, supporting features like secure boot and larger disk sizes.
These differences mean that restoring a Linux VM can require specific configuration tweaks depending on the generation.
Why Azure supports both
Gen1 maintains compatibility with older workloads, while Gen2 provides enhancements like support for UEFI, Secure Boot, and VMs with large disks. Knowing which generation your VM belongs to is crucial for restoration success.
Prerequisites for a Successful Restore
- Compatible Veeam version: Ensure Veeam Backup for Microsoft Azure is updated to support both VM generations.
- Admin privileges: Required access levels in both Azure and Veeam consoles.
- Backup verification: Confirm that recent backup snapshots are complete and error‑free.
- Storage Availability: Adequate Azure storage for temporary data during restore.
- Networking: Ensure restored VMs can access necessary subnets and security groups.
Step 1: Identify the VM’s Generation
Begin by checking the target VM’s generation:
- In the Azure portal, locate your VM.
- Navigate to “Settings → Boot diagnostics” or “Configuration”—the generation will be listed there.
- Note Gen1 or Gen2 for later steps.
Step 2: Launch the Restore Job in Veeam
- Open Veeam Backup for Microsoft Azure.
- Select “Restore”, then choose “Restore VM”.
- Browse and select the backup from the recovery point.
- Specify the restore type: opt for “Instant recovery to Azure” for quick provisioning, or full restore for permanent retention.
Step 3: Configure Restore Settings
- Resource group & location: Usually same as the original VM, but you can choose a new one.
- VM name and size: Match original configuration or choose a suitable alternative.
- Networking: Select appropriate virtual network (VNet) and subnet, and confirm IP allocation.
- Temporary disk for instant recovery: Required space must match the disk layout from backup.
Tip: For Gen2 Linux VMs, ensure UEFI boot is supported within the storage account or Temp disk settings.
Step 4: Finalise and Execute Restore
- Confirm all settings.
- Optionally tag the VM to track it in Azure.
- Click “Restore” to initiate.
- Track progress in the Veeam console.
Quick Tip: Only Gen1 Linux VMs support file-level instant recovery. Gen2 VMs require full VM recovery.
Step 5: Post‑Restore Validation
Once complete, test the following:
- VM power-on and OS boot
- Veeam confirms “Restore operation completed successfully”.
- VM starts without boot errors.
- Veeam confirms “Restore operation completed successfully”.
- Connectivity
- SSH into the restored VM.
- Ensure all network interfaces and firewalls are correct.
- SSH into the restored VM.
- Data integrity
- Verify files, databases, and configurations.
- Test critical services (e.g., web servers, application daemons).
- Verify files, databases, and configurations.
- Boot configuration (Gen2 only)
- Confirm UEFI settings and Secure Boot usage.
- Use journalctl -b to inspect boot logs for errors.
- Confirm UEFI settings and Secure Boot usage.
Best Practices and Troubleshooting
1. Always test restores
Run restores routinely not just during disasters ensuring confidence in recovery procedures and discovering hidden issues early.
2. Use service account credentials
Grant Veeam a dedicated service account with Contributor access to the target subscription to avoid permission errors.
3. Pre-provision storage
Avoid restore delays by allocating enough Temp disk space to match backup size.
4. Consider proximity placement groups
If networking matters (e.g. low latency between VMs), hosts restored VMs in the same Placement Group to improve performance.
5. Address common recovery issues
| Issue | Cause | Fix |
| Failure to boot | Incorrect generation settings or disk formatting | Confirm disk type and boot config in Azure |
| OS not booting | Gen2 grub misconfigurations | Mount and update grub via rescue mode |
| Network errors | Incorrect subnet or NSGs | Verify and reassign NIC and IP settings |
Real‑World Example
A UK‑based manufacturing client experienced a system crash on a Gen2 Linux VM critical to production. The Veeam recovery process took 8 minutes to spin up a temporary VM, followed by another 5 minutes to validate network and boot configurations. Thanks to prior testing, they went live without data loss, and their production system resumed full operation within 45 minutes.
Conclusion
Restoring Azure Linux VMs—whether Gen1 or Gen2—can be streamlined and reliable using Veeam Backup for Microsoft Azure. By following this structured approach, adhering to best practices, and performing regular recovery drills, IT teams can minimise downtime and restore confidence in their disaster‑recovery strategies.
Looking to enhance your Azure backup and recovery capabilities? Contact Cyberdan to explore managed backup services, Veeam Azure integrations, and robust disaster‑recovery solutions
