Skip to main content

During File-Level Restore (FLR) operations on an Azure VM: Only the boot area is visible; the main data drives are not accessible.

During File-Level Restore (FLR) operations on an Azure VM: Only the boot area is visible; the main data drives are not accessible.

Updated this week

Problem Description:

During File-Level Restore (FLR) operations on an Azure VM:

  • Only the boot area is visible; the main data drives are not accessible.

  • Backups may fail with the PHOENIX75 error.

Cause

  • The affected Azure VM has Azure Disk Encryption (ADE) enabled.

  • FLR is not supported for ADE-enabled disks due to encryption constraints.

  • Encryption prevents file-level access, so the FLR restore view does not show the full disk layout.

  • This limitation is consistent across Druva and other backup solutions due to Azure’s security model.

Traceback / Logs

  • FLR for non-boot (data) disks is not possible after enabling ADE.

  • Access to boot disks may also be restricted depending on encryption and permissions.

  • PHOENIX75 error: Indicates an attempt to create a disk with a name that already exists in the target resource group.

  • Backend and product teams confirmed this is a known limitation.

Resolution

  1. File-Level Recovery Needs:

    • ADE should not be enabled on disks that require FLR.

  2. ADE-Enabled Workloads:

    • Restores are possible at the full VM or disk level, though additional permissions may be required.

Did this answer your question?