Temporary Drive (D) being created on the failed over VM with ASR

Question

Hi,

When the VMs are failed over with ASR from on-premises VMware VMs to Azure, a temporary drive is getting created with drive letter D (Such drive does get created when a new VM is spin up in Azure).

If existing on-premises VMs have already a D drive and having data on it and applications using that drive, this is getting changed to E.

How can we avoid this when failing over with ASR? For 100s of number of VMs failing over and making drive changes on Azure will be a cumbersome process.

Would appreciate any suggestions

Regards,
VJ

Answer 1

A temporary drive is created by Azure compute platform for temporary storage. This is created for any VM created on Azure (VM creation experience below) not specific to ASR.

If you want to ensure windows volumes in Azure VM use the same drive letter assignment on-prem then you can run a simple command via Diskpart,

SAN Policy=OnLineAll

https://learn.microsoft.com/en-us/azure/migrate/prepare-for-migration

There have been some enhancements recently and is set automatically for i.e. VMware agentless migrations.

Failed over VM’s will then retain the same drive letters and the temporary disk will use the next available drive letter.

----------------------------------------------------------------------------------------------------------------------

If the response helped, do "Accept Answer" and up-vote it