Disk becoming protective GPT partition when on-prem VM migrated to azure using Azure Migrate

Vineet Anand 5

I am trying to migrate SQL Server VM from On prem to azure. But when i bring up the VBM in azure, i can get the disks right. they are getting converted to MBR when VM comes up in azure and the disks are unusable.

Source User's image

When migrated to azure
User's image

Please help me to resolve this.

SadiqhAhmed-MSFT 46,291 Reputation points Microsoft Employee

2024-07-22T13:16:30.2933333+00:00

@Vineet Anand Thank you for reaching out to us.

It seems like you are facing an issue with migrating SQL Server VM from On-premises to Azure. Based on the provided information, it looks like the disks are getting converted to MBR when the VM comes up in Azure, and the disks are unusable.

I would like to inform you that '/' partition should be on the OS disk, and not span other disks. Also, VMs with RDM or passthrough disks won't be replicated to Azure.

To better understand the issue, could you please provide more information on the migration process you followed? Also, please let us know if you have checked the disk size and limits as per the Azure Migrate support matrix for VMware migration - https://learn.microsoft.com/en-us/azure/migrate/migrate-support-matrix?tabs=public

If you have already checked the above points and still facing the issue, please provide us with more details on the error message or logs you are receiving. This will help us to provide you with a more accurate solution.

Hope this helps!
Vineet Anand 5 Reputation points

2024-07-27T11:53:24.5766667+00:00

We are using Azure Migrate to Migrate the VMs. Configuration server is installed in on prem and its used to replicate VM to Migrate Vault in Azure.We are using agent based replication (like treat VMs as Physical Machines.
Vineet Anand 5 Reputation points

2024-07-27T11:56:21.9133333+00:00

the issue is not yet resolved but apparently it looks like i have found the root cause. It seems to be because the sector size in the source Onpremise server is 4k while only 512 is supported on azure managed disks. there is no azure migrate support for Premium v2 disks thats supports 4k.
SadiqhAhmed-MSFT 46,291 Reputation points Microsoft Employee

2024-07-29T06:08:46.1+00:00

@Vineet Anand Thanks for the update. You are correct about the information shared. Let us know if you have any other questions.

1 answer

SadiqhAhmed-MSFT 46,291 Reputation points Microsoft Employee

2024-07-30T10:35:42.2566667+00:00

@Vineet Anand The source On-premise server is 4k while only 512 is supported on azure managed disks. There is no azure migrate support for Premium v2 disks that's supports 4k.@Vineet Anand Changed the disk on-premise and it fixed the issue.

Hope this helps others who may be looking for solution to a similar issue.

If the response helped, do "Accept Answer" and up-vote it
Please sign in to rate this answer.

1 person found this answer helpful.
Vineet Anand 5 Reputation points

2024-07-30T11:30:23.6366667+00:00

Thanks.
Only option is for us was to add new 512B disks and then for them to do the following:

1 - Stop SQL

2 - Init new disks with a new, temporary drive letter.

3 - robocopy all data from from 4K drives to 512b drives.

4 - remove drive letters from old drives and give the new, 512b drives the old letters

5 - Offline old disks before migration
6- start azure migrate replication again.

Works like charm.

SadiqhAhmed-MSFT 46,291 Reputation points Microsoft Employee

2024-07-30T12:44:50.6+00:00

@Vineet Anand Thanks once again for sharing the solution with steps.

Lyubomir Achakaknov 0 Reputation points

2024-08-07T12:23:29.16+00:00

Thank you for sharing.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Disk becoming protective GPT partition when on-prem VM migrated to azure using Azure Migrate

1 answer

Your answer