Azure Site Recovery replication error

Hello 42422946 Thank you for posting your query on Microsoft Q&A platform.

In the AWS → Azure (agent‑based) path, Azure Migrate/ASR treats your EC2 VM as a physical server and relies on the Mobility Service to enumerate and protect OS/data disks. On Nitro instances, EBS volumes are exposed as NVMe. If the guest OS has outdated/absent NVMe or ENA drivers, if any disk is Offline, or if volumes are Dynamic/RAID (not supported for exclusion and often problematic for binding), the Mobility Service can’t bind the disk and the job fails with 310006.

Follow these steps on the affected EC2 instance and the ASR appliance, then retry Enable replication.

Make sure the OS can see the disk and it’s Online:

• Open Disk Management (or run diskpart) and confirm all disks—especially the OS disk—are Online (not Offline/Detached).

    
    diskpart
    list disk
    select disk 0
    detail disk
    online disk
  

  Rerun Enable replication after correcting any Offline status.

Update AWS NVMe and ENA drivers (Nitro platform): On Windows Server 2016+ EC2 (Nitro), update AWS NVMe and ENA drivers so storage and network devices enumerate correctly for the Mobility agent. Reboot after update.

Verify disk type (avoid Dynamic/RAID for protection): ASR supports Basic disks for protection/exclusion. Dynamic disks and software RAID can cause disk‑binding failures and can’t be excluded. Where possible, convert non‑OS data volumes to Basic.

Reference: https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-aws-virtual-machines?view=migrate

Ensure the Mobility Service and replication appliance are fully up to date:

1. Update the replication appliance components first.
2. Then update the Mobility Service on the EC2 VM (portal: Replicated items → Agent update), or use the documented PowerShell/manual method.
3. Add AV exclusion for C:\ProgramData\ASR\agent.

If you specify DisksToInclude in automation :Enumerate actual disk paths (Get-Disk, wmic diskdrive) and ensure the exact \.\PHYSICALDRIVE# values you pass exist and are online. Mismatches will trigger 310006.

If you intend to exclude disks, remember only Basic (non‑OS) disks are eligible, and Mobility Service must already be installed before you can configure disk exclusion in Replication settings → Advanced → Disks.

Verify and retry:

After updating NVMe/ENA and confirming disks are Online/Basic, update the Mobility Service to match the appliance version.

Retry Enable replication from the Azure Migrate blade and watch for a clean “Protecting” → “Initial replication” transition.

If it fails again, collect logs from %ProgramData%\ASR\agent\logs (source VM) and the appliance, and review for disk enumeration entries.

If you need any further assistance, please feel free to reach out.

Thanks,

Suchitra.