This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 89%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETC%3C/text%3E%3C/svg%3E)
HI everyone,
Hope you can help on this. I have two production servers which work with each other, one a front end app IIS server, and one is a SQK server. Both are running on a same hyper-v host.
Now I would like to run an upgrade on the SQL server from 2014 to 2019. To test out the upgrade and their functionalities afterwards, I would like to "clone" these two servers by exporting and importing them to a different hyper-v host. However, I just want them to run in its own network so that they both can still communicate between only themselves, but should not accessible by other machines (including all physical and virtual machines).
I think i should create a "internal private switch/network"? Please correct me if I am wrong.
Thank you for your help in advance.
Takami Chiro
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
You can create a private virtual switch if you want the VMs to be completely isolated.
Best Regards,
Ian Xue
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you Ian Xue!! Tse Tse li de bon mon :)
HI Dave,
Thank you for the info. I do not want the two "cloned" VMs affecting the live production VMs which have the same name. I thought either private switch or internal switch could be my choice but not external switch?
Takami Chiro
Private or internal would not be successful to reach the VM on other host.
--please don't forget to upvote and Accept as answer if the reply is helpful--
So I just reread above, if both VMs will be on same host and you want no outside connectivity then by all means use an internal vSwitch.
--please don't forget to upvote and Accept as answer if the reply is helpful--
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
You'll need to use an external vSwitch in order to communicate outside the given host to other host. Create external vSwitches (using a dedicated interface) on each host, then plug them into a separate physical switch so the two can communicate.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
