instant vm restore lost network configuration

[matteu]

Hello,

I'm trying to use the cmdlet Start-VBRViComputerInstantRecovery to migrate Hyper-v vm to vmware but I lost the network configuration inside my guest OS if I use powercli. I don't have any issue with GUI.

I don't have any error. This is what my command looks like :

Code: Select all

Start-VBRViComputerInstantRecovery -RestorePoint $restorepoint -Server $server -CacheDatastore $datastore -PowerOnAfterRestoring:$true -ConnectVMToNetwork -SourceNetwork $SourceNetwork -TargetNetwork $TargetNetwork -Reason "VM migration" -Verbose

I don't understand what I forgot. On the documentation, I can see I need to use ConnectVMToNetwork and I did it.

[Mildur]

Hi Matteu

but I lost the network configuration inside my guest OS if I use powercli

Is this about changing the NIC adapter from E3000 to VMXNET3? I would expect that you have to reconfigure the network configuration inside the VM. If you change the type with PowerCLI, windows will see the network card as a new one.

[matteu]

No it isn't.
I don't make any change on my test here. I just try to migrate VM from HV to VM without any change. I keep E1000 on my test like it does with GUI but I have this issue

[david.domask]

Hey @matteu,

Could you reproduce the issue and raise a Support Case? Use the 3rd radio option when following https://veeam.com/kb1832 and select the Veeam server, and note the time and date of the test. (for the viewing audience, we want the server export in this case just to get the powershell and restore logs. In any other case you have with failing jobs, you want to use the 1st option and select the relevant jobs, always. Server exports will not get the necessary information)

At first blush seems weird and just would be great to see what happens in the logs.

[matteu]

Thanks for your message.

Case #05383952

[david.domask]

Thanks!

I've responded on the case, but as I see it, it's not (yet) related to the cmdlet but about the target network you're attempting to connect to. So cmdlet seems to work "okay", but let's continue in the case.

Edit: (I think I see the issue, and perhaps not about the target but the _source_, but let's continue in the case)

[matteu]

Unfortunately if I don't use source network, Veeam can't map source and target network I suppose because they have not the same name.

I try to test this command which is probably the simpliest possible but it's not working when I use powershell (it's working if I only use GUI) :

Code: Select all

$backup = Get-VBRBackup -Name "test v2v"
$restorepoint = Get-VBRRestorePoint -Backup $backup | Sort-Object -Descending CreationTime | select -First 1
$srv = Get-VBRServer -Name "192.168.1.2"
$SourceNetwork = Get-VBRComputerNetworkInfo -RestorePoint $restorepoint
$TargetNetwork = Get-VBRViServerNetworkInfo -Server $srv.name| Where-Object { $_.NetworkName -eq "VM Network" }

Start-VBRViComputerInstantRecovery -RestorePoint $restorepoint -Server $srv -SourceNetwork $SourceNetwork -TargetNetwork $TargetNetwork -PowerOnAfterRestoring -ConnectVMToNetwork

(no problem for IP address in clear text, it's a lab ip)

[matteu]

The incident didn t moove from free support to paid support since I provide support id.
I don t know if this is normal

[david.domask]

HI Matteu,

We're in the process of this, but we need you to have your client set you as a case administrator as per https://veeam.com/kb2211

[matteu]

It's done

[david.domask]

Thanks Matteu!

I'm moving the case to the paid queue then and also putting one of my engineer's on it to research while I'm doing testing as well, so should have updates for you soon.

[matteu]

Thanks

He contacted me but the first idea was not the good one
Maybe the second !

Thanks for your help

[matteu]

Just to keep informed :
Case is on r & d group and I m waiting return back. First Engeneer support probably didn t try to reproduce my issue and after I ask for escalation the second reproduce it and have the same issue

[matteu]

Hello,

Just to keep everyone informed.
R&D build a fix and it's now working. I suppose it will be integrated on the next version.

[Mildur]

Hi Matteu

Thanks for the update.
I'm glad that it is working now.