Figure 8.3 Configuring an alternate IP configuration to be used during failover
It is important to understand that this process works by Hyper-V updating the virtual
machine through the Windows Server Hyper-V Integration Services running on the
virtual machine. This works only on synthetic network adapters, not legacy network
adapters, and it requires Windows XP SP2/Windows Server 2003 SP2 and newer to be
running on the virtual machine to work. This also works with Linux virtual machines
that are running the latest Linux distributions. A good practice is to complete the
failover TCP/IP configuration on the primary virtual machine with its normal IP
configuration. That way, if the replica is ever activated, replication is reversed, and the
virtual machine is then failed back to what was the primary, and the correct IP address
for the primary location can automatically be put back.
INJECT IP CONFIGURATION OUTSIDE HYPER-V REPLICA BY
USING POWERSHELL
Hyper-V Replica offers the ability to inject an IP address into a virtual machine;
you can also use this functionality outside Hyper-V Replica.
To perform the injection with PowerShell, use the following code, which leverages
the Msvm_GuestNetworkAdapterConfiguration class