<div>
Is there a question here? &nbsp;Are you using replication between the 2 host machines? Export/Import from 1 to the other?
</div>


Is there a question here?  Are you using replication between the 2 host machines? Export/Import from 1 to the other?

<div>
<div class="content wysiwyg-content">
I currently have two PHYSICAL servers with some <br />
HyperV VMs on them in a non-HA config, <br />
both PHYSICAL boxes stand-alone.<br />
<br />
I assume I should have the same attached &quot;VM Switch Names&quot; <br />
on both PHYSICAL servers (i.e. vSwitch01, vSwitch02, etc) for <br />
easy HyperV VM moving if needed ?<br />
&nbsp; ** i.e. I decide to move VM #1 from PHYSICAL server #1 <br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;to PHYSICAL server #2 for some reason<br />
<a href="https://filedb.experts-exchange.com/incoming/2015/11_w45/997141/s479.jpg" target="_blank" class="file-inline" title="2 (48 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>s479.jpg</a>
</div>
</div>


s479.jpg

I currently have two PHYSICAL servers with some 
HyperV VMs on them in a non-HA config, 
both PHYSICAL boxes stand-alone.

I assume I should have the same attached "VM Switch Names" 
on both PHYSICAL servers (i.e. vSwitch01, vSwitch02, etc) for 
easy HyperV VM moving if needed ?
  ** i.e. I decide to move VM #1 from PHYSICAL server #1 
             to PHYSICAL server #2 for some reason

Windows 2012 R2 HyperV -- same switch name for easy restore ?

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.