Skip to main content

[Workaround exists] Run VM from Backup using dvSwitch (Continued from Beta-Section)

Thread needs solution

Thanks for the new release, have done some tests on my reports from late Beta/Release version.

I can confirm Run VM from Backup generally works now [ABR-109259].

But have this network issue reported in thread "122385: [Need Verify] Replication / Test replica / dvSwitch" (Archived Beta forum).

The task succeeds when not selecting a network on the "Run VM from Backup" dialog, when a specific dvSwitch-Network is select it fails on VM creation.

mms.log wrote:
| Fehler 0x530128: Das Objekt oder Element, auf das Bezug genommen wurde, konnte nicht gefunden werden.
| Zeile: 0xc7610e0a857bedd2
| Datei: k:\3596\enterprise\virtualware\raw\vmware\vix_soap\vix_supp_impl.cpp:346
| Funktion: `anonymous-namespace'::VixSuppImpl::WaitForTaskResult
| fault: MethodFault
| $module: esx_srv_vsa64_3596
|
| Fehler 0x530128: DVPortgroup dvportgroup-85 wurde nicht gefunden

| Zeile: 0xc7610e0a857bedd2
| Datei: k:\3596\enterprise\virtualware\raw\vmware\vix_soap\vix_supp_impl.cpp:346
| Funktion: `anonymous-namespace'::VixSuppImpl::WaitForTaskResult
| fault: NotFound
| $module: esx_srv_vsa64_3596

Will do some more tests on selecting network, also for replica tasks.

Thanks!

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Raphael,

Network on replicated/Run from backup VM is unavailable/disconnected because the dvSwitch port ID on replicated/mounted and the original VM is the same, thus causing the conflict while original VM still runs on the same vCenter. There is no simple way to address this problem in fact, since one possible solution imply that the port ID on replica/mounted VM will not match the original VM (i.e. we'll generate a new vNIC and connect it to new port ID) which is also not good and I believe it would be even worse than the current behavior. An alternative is to add ability to define the port ID in the replication/Run VM from backup wizards and this has to be implemented separately.

P.S. Internal tracking ID for this issue is ABR-109223. There is no ETA for fixing it yet.

Thank you.

Hi Vasily,

thanks for your Info and tracking Id.

It is working when not selecting a dvSwitch, so a functional workaround exists. I will mark this topic for further testing when a fix becomes available.