Azure Migrate

Question

I'm trying to migrate an on prem vm from hyper-v host into Azure using Azure Migrate.

I got the VM into a protected state with replication completing successfully.

When I attempt a test migration i get error id: 499 an internal error occurred retry last action. if the issue persists contact support.

Now its been a few days and replication has stopped and its in a critical state in azure migrate.

Does anyone know what this might mean?

I'm trying to raise a support ticket for the client but our partner portal is not allowing me to log technical support tickets for any clients even after activating our silver partner benefits.

I've logged a ticket for that issue in the partner portal but I'm getting no response from them since they last said follow this guide. It was exactly the guide I was following in the first place and now full silence from them!

Anyway that is another issue but anyone experienced error id 499 before?

I wonder if I need to just stop replication and start again?

If i stop replication its not clear what happens. does it just remove the server from the replicating servers area in azure migrate and make it available to start a new replication?

Does it do anything to the onprem server like remove it or anything I would not be expecting?

I've gone through the guide etc: https://learn.microsoft.com/en-us/azure/migrate/tutorial-migrate-vmware#complete-the-migration but its still not clear.

Anyone able to offer any help while I wait a few days for partner support to sort out why I cant log azure technical support tickets.

Thanks!

Answer 1

@Ian Waters Sorry for the painful experience. Just wanted to check few things to isolate the issue.

Ensure that the resource group where this migration project/recovery services vault exist is not being applied any resource lock (cannot-delete lock/read-only lock)

***I wonder if I need to just stop replication and start again?****
When you stop replication, the Azure Migrate: Server Migration tool cleans up the managed disks in the subscription that were created for replication. This happens only when the migration is completed. But in your case the test migration failed and I think it will perform clean up operation, post that you should be able to start replication again. I personally haven't tried this but since this is test migration you may give a shot.

Does it do anything to the onprem server like remove it or anything I would not be expecting?
It doesn't do anything unexpected.

Let me know how it goes!