question

BillTkach-2852 avatar image
0 Votes"
BillTkach-2852 asked BillTkach-2852 commented

Running replication between a Windows Server 2022 Hyper-V system and a Windows 2019 Hyper-V server.

Running replication between a Windows Server 2022 Hyper-V system and a Windows 2019 Hyper-V server.

Replication works if I replicate from 2019 to 2022.
I cannot replicate in the opposite direction.
I'm wondering if the hyper-v version would cause the 2022 to 2019 replication problem, and if there is a specific way to find out, other than the Event ID 32000 error that comes up on the Hyper-v hosts.

Also, the replications I setup from 2019 to 2022, worked for several weeks, and then stopped working.
They stopped working on the day I rebooted the 2022 hyper-v system. not sure if there is a correlation.
Using Kerberos.
The 2022 system has two IP connections, on two networks, not sure if that can cause a problem.

Again it worked, and then stopped working.

This happened once before, so I deleted the replication set, and recreated it, and it started to work again. I'm not sure why it stops replicating.

Thanks

windows-server-hyper-v
· 1
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BillTkach-2852 avatar image BillTkach-2852 ·

The problem appeared to be with the multiple network adapters connected, and Kerberos not liking this situation.

So Instead of multihoming the Hyper-V host, I removed one of the adapters from the host, by making it unavailable to the host system.
I can still access it through the other connection, and my VM's can use either network attached to the host.

This made it so the replication works between systems.

In my case receiving replication server is at a different site, connected via fibre. This allows me to replicate to a device on the same IP range, so if the original server bursts into flames or is stolen, the new VM can be spun up on the same network, even though it's a fibre's length away, in this case 3km.

Thanks for any help.

0 Votes 0 ·

1 Answer

LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered BillTkach-2852 commented

Hello

Thank you for your question and reaching out.

I can understand you are facing Hyper-V replication issues between 2019 and 2022 server.

  1. Please try to reset if any proxy server activated , you can use below command to reset it.

"netsh winhttp reset proxy"

  1. Disable any Antivirus program or Windows firewall you may have for temporary purpose.

  2. Perform the following steps on the Hyper-V host machine:
    A. Logon as a Domain Administrator
    B. Install the Group Policy Management feature from the Server Manager console
    C. After installation, open the GPMC MMC snap-in and browse to the policy that manages User Rights
    D. Edit the policy to include NT Virtual Machine\Virtual Machines in the entries for Log on as a Service
    E. Close the policy editor and initiate a gpupdate /force on the Hyper-V host computer to refresh policy. (You may need to wait several minutes for Active Directory replication to occur).


--If the reply is helpful, please Upvote and Accept as answer--

· 1
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BillTkach-2852 avatar image BillTkach-2852 ·

I think that is from this page

https://docs.microsoft.com/en-us/answers/questions/491733/hyper-v-replication-failed.html

I did those steps, but it did not help.

0 Votes 0 ·