VMware Cloud Community
Jwoods
Expert
Expert
Jump to solution

vDS to vDS Cold migration

Is there an easier way to cold migrate a VM from vDS to vDS without removing the vNIC?

My current environment has 2 physically separated datacenters with about 15 hosts in each.  vCenter is configured with each physical datacenter having a single 15-host Datacenter/Cluster and vDS defined for each.

The current process prior to cold migration is to remove the vNIC(s), then migrate the VM to the desired location.  Is there a better or easier way of doing this?  Would labeling my dvPgs exactly the same resolve this issue?

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
peetz
Leadership
Leadership
Jump to solution

For such scenarios we have created the following workaround in our environment:

Create an extra vDS (we named it TransferSwitch), add all hosts from all datacenters/clusters to it, but without any physical uplink.

A cold migration process from one datacenter/cluster to another is then done in three steps:

1. Connect the VM's NIC to the TransferSwitch

2. Cold migrate the VM to the destination

3. Connect the VM's NIC to the destination vDS

This avoids removing/re-adding the VM's NICs and all consequences (like a new device being detected in the Guest OS, with a different MAC address).

You may create the TransferSwitch just temporarily for each VM migration, but we decided to just keep it permanently.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de

View solution in original post

0 Kudos
4 Replies
peetz
Leadership
Leadership
Jump to solution

For such scenarios we have created the following workaround in our environment:

Create an extra vDS (we named it TransferSwitch), add all hosts from all datacenters/clusters to it, but without any physical uplink.

A cold migration process from one datacenter/cluster to another is then done in three steps:

1. Connect the VM's NIC to the TransferSwitch

2. Cold migrate the VM to the destination

3. Connect the VM's NIC to the destination vDS

This avoids removing/re-adding the VM's NICs and all consequences (like a new device being detected in the Guest OS, with a different MAC address).

You may create the TransferSwitch just temporarily for each VM migration, but we decided to just keep it permanently.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
0 Kudos
Jwoods
Expert
Expert
Jump to solution

Andreas,

Thanks for the response.  I'm a bit confused here.  Bare in mind that I'm still learning about dvSwitches and their intricacies.  With that, isn't it true that a  dvSwitch needs at least one uplink for each host for communication with one another?  If I create a dvSwitch with no uplinks wouldn't vcenter give a warning requesting the uplink?

0 Kudos
peetz
Leadership
Leadership
Jump to solution

No, you won't get a warning. It's perfectly okay to create a vDS without any physical uplinks (just as it is okay to create a standard vSwitch without uplinks).

Of course, a VM attached to this vDS won't be able to communicate over the network. However, you only attach a VM to that vDS for moving it between clusters while it is powered off.

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Jwoods
Expert
Expert
Jump to solution

Andreas Peetz wrote:

...just as it is okay to create a standard vSwitch without uplinks

I considered this, but wasn't sure if the same applied to vDS.  Many thanks for your help!
0 Kudos