Server replication, remote site
Hello
I am facing a problem, my hyper V server has only one physical network card, and my provider is not able to interconnect my two servers via their solution (Vrack) which requires a physical network card dedicated to this
interconnection.
My configuration:
HV1:
1 VM of production + 1 VM Domain controller
HV2:
1VM which will be the replicate of the production VM + 1
testing VM
My need :
Replicate production Virtual Machine + Join
production and testvirtual machinesto the domain.
The replication method (HyperV or Veeam) does not matter to me, as long as it works.
Problem:
I only have ONE physical card on my HV’s
I do not have access to routers that bridge between my hypervisors and the internet
Do you have any ideas
Is it technically feasible with a single network card?
Thanks !!
Can not access to internet virtual machine
Hello,
I have a server 2016 STD with role Hyper V, and a virtual machine SRV2019 STD
I have on my physical server an "Ethernet" card with ip as a public IP of my provider
Internet works perfectly
In the Hyper V Manager I created an "External Network" virtual switch using my Intel physical adapter
in the configuration of the virtual machine, I assigned him the virtual card "VSwitch"
When I start the VM, it does not have internet.
note: Hyper-V Extensible Virtual Switch is checked on the "Ethernet" card and not "vEthernet", I do not know if it’s good
OnPhysical Machine :
Carte Ethernet vEthernet (VSwitch) : Suffixe DNS propre à la connexion. . . : Description. . . . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3 Adresse physique . . . . . . . . . . . : 00-25-90-D5-xx-xx DHCP activé. . . . . . . . . . . . . . : Non Configuration automatique activée. . . : Oui Adresse IPv6 de liaison locale. . . . .: fe80::6961:b193:bc21:xxxxx(préféré) Adresse IPv4. . . . . . . . . . . . . .: 37.187.xx.xx(préféré) Masque de sous-réseau. . . . . . . . . : 255.255.255.0 Passerelle par défaut. . . . . . . . . : fe80::205:73ff:fea0:xxxx 37.187.xx.xx IAID DHCPv6 . . . . . . . . . . . : 385885584 DUID de client DHCPv6. . . . . . . . : 00-01-00-01-24-58-E9-A2-00-25-90-D5-FE-xx Serveurs DNS. . . . . . . . . . . . . : 213.186.xx.xx NetBIOS sur Tcpip. . . . . . . . . . . : Activé
On the virtual machine
Carte Ethernet Ethernet: Suffixe DNS propre à la connexion. . . : Description. . . . . . . . . . . . . . : Microsoft Hyper-V Network Adapter Adresse physique . . . . . . . . . . . : 00-25-90-D5-xx-xx DHCP activé. . . . . . . . . . . . . . : Oui Configuration automatique activée. . . : Oui Adresse IPv6 de liaison locale. . . . .: fe80::6961:b193:bc21:xxxxx(préféré) Adresse IPv4. . . . . . . . . . . . . .: 169.254.178.75(préféré) Masque de sous-réseau. . . . . . . . . : 255.255.0.0 Passerelle par défaut. . . . . . . . . : fe80::205:73ff:fea0:xxxx
I understand that in 169 it can not work but I do not understand what I have to do
Can you helping me ?
Thanks
- Top 20 articles for vRealize Operations, December 2020 January 25, 2021
- Top 20 articles for EUC, December 2020 January 25, 2021
- New KB articles published for the week ending 17th January, 2021 January 25, 2021
- New KB articles published for the week ending 10th January, 2021 January 15, 2021
- New KB articles published for the week ending 3rd January,2021 January 7, 2021