Azure Migrate - Replication Item Fails Error 320015 System disks are missing for machine

Question

Azure Migrate - Replication Item Fails Error 320015 System disks are missing for machine

Jim Pacella 0

I've been trying to run Migrate for a Physical VM migration to Azure VM.

The source VM has 3 disks. System Disk is 200GB and there are two Data Disks, each being 2TB.

So I installed the Migration Server and the Replication Server and had started a Migrate Execution, with all volumes.

When the migration finished with the system disk, it started to do the first data disk but I kept getting errors regarding network latency being too high to keep up with the replication data load.

So I stopped replication, and I deleted the Migration and then recreate a new Execution and when configuring the replication settings, I excluded the two data disks. When I launch the Replication, I keep getting error 320015. "System Disks are not included in the replication disk set for machine"

Is it possible that one of the two data disks also need to be selected for some reason?

Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-02T19:22:08.82+00:00

Hello Jim Pacella

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

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-03T18:08:46.9766667+00:00

Hello Jim Pacella

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thank you.
Jim Pacella 0 Reputation points

2026-07-06T14:07:58.3+00:00

Hi I'm back from holiday. I do see that the Page File is on the data disk. I'm going to assume this is why the data disk is viewed as required.

I'm going to move the page file back to the system drive and reattempt the replication.
Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-06T14:16:56.1533333+00:00

Hello Jim Pacella

Sure, please try and let us know the results.

Thank you.
Jim Pacella 0 Reputation points

2026-07-06T15:27:22.3366667+00:00

Ok, so I did migrate the page file from the data drive to the system drive. I rebooted the source server VM and checked into Disk Management. All the system functions are now exclusively on the C Drive.

So back in Azure Portal, I went to the Replicated Items screen in the Vault to restart the existing job. Unlike before where I got the job failure very quickly after restarting it, this time (after the page file relocation and reboot), it took almost 10 minutes to get to the "Enable replication" item in the Site Recovery Job.

The "Prerequistes check for enabling protection" took 3 minutes. "Installing Mobility Service and enabling replication" took 8 minutes, and "Enable Replication" failed right away. The errors are:

Error ID320015 Error Message The system disks '{3316970610}' are missing for machine '[Machine Name]'. Possible causes System disks are not included in the replication disk set for machine '[Machine Name]'. Recommendation Ensure that the system disks have also been included in the replication disk set for the machine '[Machine Name]'. After that retry the enable protection operation. If the issue persists, contact support. First Seen At7/6/2026, 10:15:00 AM Error ID539 Error Message The requested action couldn't be performed by the Replication Provider. Possible causes The Provider action failed. Check other errors for more information. Recommendation Resolve the issue and retry the operation. First Seen At7/6/2026, 10:15:00 AM

So what I'm going to do now, is go back to the Migration Wave Planning and Stop Replication and restart it and going through the settings again... and for it to create the new Replication jobs in the Vault.
Jim Pacella 0 Reputation points

2026-07-06T15:56:35.5966667+00:00

I get confused with how to reconfigure a Wave Plan so that I can go through the steps of allocating the destination VM's settings and disk selections. The Wave Plan was based on an assessment.

Last week when I was trying to get the replication to work, just restarting the migration allowed me to reconfigure the VM and Disk selections, but today if I "Execute" the stopped Wave Plan, it doesn't allow me to do that.

I even deleted the Wave Plan and then created a new one from the assessment and it took the settings from the prior Wave Plan (so not allowing VM allocation or disk selection).

Also, last week's Wave Plan only had one workload for the Server, but now it's configuring all the workloads, including FIle Shares that point to Data Disks that I dont want to migrate.

So I've been in a loop of attempting to "restart" with new settings. Any ideas?
Jim Pacella 0 Reputation points

2026-07-06T17:19:52.4+00:00

Update: I recreated the Assessment and the Wave Plan, but I then remembered that the replication job needs to be created in the Replication Items section. So I created the replication and this time I selected the system drive and Data Drive 1 and the Execution of the Migration is now in Synchronized Status.. but that's still going to give the original problem with the network latency that prompted me to attempt a new replication.

So there is something on Data Disk 1 that the Migrate wants that is not apparent by what Disk Management is showing me. How can I exclude Data Disk 1?
Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-08T12:54:46.4833333+00:00

Hello Jim Pacella

Thank you for the update.

The fact that replication reaches Synchronized status when Data Disk 1 is included suggests that Azure Migrate currently considers that disk part of the required replication set. At this point, I'd like to better understand the disk configuration before suggesting any next steps.

Could you please help with the following information:

A screenshot of Disk Management (diskmgmt.msc) showing all disks and partitions.

A screenshot of the Replication Items > Configure Replication > Disks page showing the disk selections.

Is Data Disk 1 a Basic Disk or a Dynamic Disk?

Are any volumes configured as Spanned, Striped, Mirrored, RAID, or Storage Spaces?

Does the server use any iSCSI, SAN-attached storage, or third-party volume management software?

What is the operating system and version of the source server?

When Data Disk 1 is excluded, does Azure Migrate report only Error 320015, or are there any additional warnings/details shown in the job logs?

Once we review the disk layout and replication configuration, we can determine why Azure Migrate is identifying Data Disk 1 as a required disk and whether there is a supported way to proceed without replicating it.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-09T06:54:03.84+00:00

Hello Jim Pacella

Could you please share us the above asked details?

Thank You.

2 answers

Your answer

Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-02T19:22:08.82+00:00

Hello Jim Pacella

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

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-03T18:08:46.9766667+00:00

Hello Jim Pacella

Could you please let us know if the comment above resolved your issue? If you need any further assistance, feel free to reach out—we're always here to support you.

If you found the comment helpful, please consider clicking "Upvote it."

Thank you.
Jim Pacella 0 Reputation points

2026-07-06T14:07:58.3+00:00

Hi I'm back from holiday. I do see that the Page File is on the data disk. I'm going to assume this is why the data disk is viewed as required.

I'm going to move the page file back to the system drive and reattempt the replication.
Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-06T14:16:56.1533333+00:00

Hello Jim Pacella

Sure, please try and let us know the results.

Thank you.
Jim Pacella 0 Reputation points

2026-07-06T15:27:22.3366667+00:00

Ok, so I did migrate the page file from the data drive to the system drive. I rebooted the source server VM and checked into Disk Management. All the system functions are now exclusively on the C Drive.

So back in Azure Portal, I went to the Replicated Items screen in the Vault to restart the existing job. Unlike before where I got the job failure very quickly after restarting it, this time (after the page file relocation and reboot), it took almost 10 minutes to get to the "Enable replication" item in the Site Recovery Job.

The "Prerequistes check for enabling protection" took 3 minutes. "Installing Mobility Service and enabling replication" took 8 minutes, and "Enable Replication" failed right away. The errors are:

Error ID320015 Error Message The system disks '{3316970610}' are missing for machine '[Machine Name]'. Possible causes System disks are not included in the replication disk set for machine '[Machine Name]'. Recommendation Ensure that the system disks have also been included in the replication disk set for the machine '[Machine Name]'. After that retry the enable protection operation. If the issue persists, contact support. First Seen At7/6/2026, 10:15:00 AM Error ID539 Error Message The requested action couldn't be performed by the Replication Provider. Possible causes The Provider action failed. Check other errors for more information. Recommendation Resolve the issue and retry the operation. First Seen At7/6/2026, 10:15:00 AM

So what I'm going to do now, is go back to the Migration Wave Planning and Stop Replication and restart it and going through the settings again... and for it to create the new Replication jobs in the Vault.
Jim Pacella 0 Reputation points

2026-07-06T15:56:35.5966667+00:00

I get confused with how to reconfigure a Wave Plan so that I can go through the steps of allocating the destination VM's settings and disk selections. The Wave Plan was based on an assessment.

Last week when I was trying to get the replication to work, just restarting the migration allowed me to reconfigure the VM and Disk selections, but today if I "Execute" the stopped Wave Plan, it doesn't allow me to do that.

I even deleted the Wave Plan and then created a new one from the assessment and it took the settings from the prior Wave Plan (so not allowing VM allocation or disk selection).

Also, last week's Wave Plan only had one workload for the Server, but now it's configuring all the workloads, including FIle Shares that point to Data Disks that I dont want to migrate.

So I've been in a loop of attempting to "restart" with new settings. Any ideas?
Jim Pacella 0 Reputation points

2026-07-06T17:19:52.4+00:00

Update: I recreated the Assessment and the Wave Plan, but I then remembered that the replication job needs to be created in the Replication Items section. So I created the replication and this time I selected the system drive and Data Drive 1 and the Execution of the Migration is now in Synchronized Status.. but that's still going to give the original problem with the network latency that prompted me to attempt a new replication.

So there is something on Data Disk 1 that the Migrate wants that is not apparent by what Disk Management is showing me. How can I exclude Data Disk 1?
Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-08T12:54:46.4833333+00:00

Hello Jim Pacella

Thank you for the update.

The fact that replication reaches Synchronized status when Data Disk 1 is included suggests that Azure Migrate currently considers that disk part of the required replication set. At this point, I'd like to better understand the disk configuration before suggesting any next steps.

Could you please help with the following information:

A screenshot of Disk Management (diskmgmt.msc) showing all disks and partitions.

A screenshot of the Replication Items > Configure Replication > Disks page showing the disk selections.

Is Data Disk 1 a Basic Disk or a Dynamic Disk?

Are any volumes configured as Spanned, Striped, Mirrored, RAID, or Storage Spaces?

Does the server use any iSCSI, SAN-attached storage, or third-party volume management software?

What is the operating system and version of the source server?

When Data Disk 1 is excluded, does Azure Migrate report only Error 320015, or are there any additional warnings/details shown in the job logs?

Once we review the disk layout and replication configuration, we can determine why Azure Migrate is identifying Data Disk 1 as a required disk and whether there is a supported way to proceed without replicating it.

Thanks,

Suchitra.
Suchitra Suregaunkar 16,210 Reputation points Microsoft External Staff Moderator

2026-07-09T06:54:03.84+00:00

Hello Jim Pacella

Could you please share us the above asked details?

Thank You.

Answer 1

hi Jim Pacella & thx for sharing urs issue here at Q&A portal,

320015 usually means Azure Migrate doesn't think the boot/system disk is part of the replication set. It doesn't necessarily mean you need to replicate the data disks. If u stopped replication, deleted the migration, and recreated it, I'd first verify which disk Azure Migrate is identifying as the system disk. On some physical machines, especially if there are separate boot, EFI, or reserved partitions, the OS may span more than one volume even though Windows shows a single system drive. It's also possible that the appliance retained stale disk metadata from the previous replication attempt. In that case, simply creating a new replication execution may not be enough if the machine inventory wasn't refreshed.

I wouldn't expect the 2 TB data disks to be required unless one of them contains a system or boot partition. I'd check the source VM with Disk Management (or diskpart) to confirm where the EFI/System Reserved partitions are located. If any of those partitions reside on a different disk, that disk must be included in replication. If the system partitions are all on the 200 GB disk and the error still occurs, this points more toward stale replication metadata or an Azure Migrate issue. I'd collect the appliance logs and open a support case, as the migration service may be incorrectly identifying the replication disk set.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/

Answer 2

Hello Jim Pacella

Yes, it is possible that one of the 2‑TB disks also needs to be selected, but only if Azure Migrate identifies that disk as containing required system/boot components.

The error 320015 ("System disks are not included in the replication disk set for machine") indicates that Azure Migrate does not see all required system disks in the selected replication set. While data disks can be excluded from replication, the disk containing the operating system boot components must be included. During replication configuration, Azure Migrate requires the OS (boot) disk to be selected. Excluded disks are not migrated to the target Azure VM.

To determine whether one of the 2‑TB disks is required, please check the disk layout on the source server using Disk Management and identify where the boot-related partitions are located (for example, the EFI System Partition or System Reserved partition). If any of those partitions reside on one of the 2‑TB disks, that disk must also be included in replication. If all boot/system partitions are located on the 200‑GB disk, then the 2‑TB data disks shouldn't be required for replication.

Reference:

If you're unsure which disk contains the boot/system partitions, please share a screenshot of Disk Management showing all disks and partitions, and we can help review the configuration further.

Thanks,

Suchitra.