Open theheatDK opened 3 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @shijojoy.
Author: | theheatDK |
---|---|
Assignees: | - |
Labels: | `Migrate`, `Service Attention`, `customer-reported`, `needs-triage`, `question` |
Milestone: | - |
Hi @theheatDK, Apologies for the delayed response. I see that this issue was opened for a while and no further activity had taken place. So wanted to check if you are still looking for assistance on this query or was the issue resolved? Please let us know .
Thank you
Hi @KranthiPakala-MSFT No, it was never resolved. We gave up on scripting this and did everything manually in the Azure Portal. As far as I can tell most of the Azure Migrate cmdlets do not work for Hyper-V. Luckily all our other Azure Migrate projects have been VMware. Regards Peter
@theheatDK - I think Az Migrate module is used for agentless scenario (vmware). For migrating of physical and hyper-v workloads it still uses ASR in the backend, hence you should be using Az.RecoveryServices cmdlets
@NimalDas - You are right that ASR are used in the backend, but I do not believe you can do anything via Az.RecoveryServices. I created a support ticket regarding some problems with Azure Migrate on Hyper-v and they asked if I had done anything via ASR, because this could cause problems. Everything should be done via Azure Migrate.
Since Az.Migrate only supports VMware this should be stated in the documentation. We have spend hours trying to get it to work with Hyper-V.
@theheatDK - I agree that this should be made clear in the documentation. However it is not clear when you say "if I had done anything via ASR, because this could cause problems. Everything should be done via Azure Migrate." Can you explain a bit more on what you were trying to achieve?
@NimalDas - When you use Azure Migrate to migrate Hyper-V guests to Azure you configured Azure Migrate to do the migration. You do everything via Azure Migrate in the Azure Portal. Behind the scene, ASR is configured in Azure. You install an ASR agent on each node of the Hyper-V cluster, but otherwise, you are not aware that ASR is used. Since ASR is used you can go to the ASR in the Azure Portal and do stuff, but I was told by the support to never do that. Using Azure Migrate for Hyper-V is very pain full since there is no PowerShell cmdlet for this. You have to manually do everything via Azure Migrate in the Portal. You have to manually go tho each VM and change IP, disk, license, etc. When you have 100+ servers this quickly gets old :-/ Hyper-V is a Microsoft product. It is difficult to understand why experiences have to be so bad for migrating Hyper-V versus VMware where you have the possibility to do most of the stuff via Az.Migrate. That said Az.Migrate for VMware is still missing some steps. You cannot do the assessments or get the VMs in the assessment groups. We have found some PowerShell script that uses the REST API to set up assessments etc. But it would be nice to have support for the whole process in Az.Migrate :-) Regards Peter
You have to manually go tho each VM and change IP, disk, license, etc. When you have 100+ servers this quickly gets old :-/
Even with 20 machines that's a lot of manual migration steps and then the jobs also have to be completed one by one in the gui :-(
Hi @dingmeng-xue and @KranthiPakala-MSFT. Is there any progress on this? Still get "Cannot bind argument to parameter 'ResourceName' because it is an empty string." when using some of the Cmdlets of Az.Migrate against an existing Migrate Project with physical servers being migrated...
same problem here. My project is Physical machines, and when i use 'Get-AzMigrateServerReplication' command, return this: Get-AzMigrateServerReplication: Cannot bind argument to parameter 'ResourceName' because it is an empty string.
But i declare "ResourceGroupName"
same problem here. My project is Physical machines, and when i use 'Get-AzMigrateServerReplication' command, return this: Get-AzMigrateServerReplication: Cannot bind argument to parameter 'ResourceName' because it is an empty string.
But i declare "ResourceGroupName"
We are also having the same issue. Any updates on this or are we stuck using the GUI?
Description
Hi, Whichever way I try to call Get-AzMigrateServerReplication it fails with "Cannot bind argument to parameter 'ResourceName' because it is an empty string."
Steps to reproduce
Environment data
Module versions
Debug output
Error output