Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 19461

Hyper-V 2019 VM Cluster Replication

$
0
0
Ever since upgrading our 2 Hyper-V clusters to 2019 from 2012 R2 when trying to set up a new VM replication I get errors. Works for existing VMs replicating that were created before the upgrade but any new VMs fail. Enabling the replication seems to create the VM fine on the replica and creates drives at 4,096KB ready for replication but trying to start the initial replication fails with the error:

Start-VMInitialReplication : Hyper-V failed to start replication for virtual machine 'VM': Operation aborted
(0x80004004). (Virtual machine ID E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5)
Hyper-V could not find the virtual machine 'VM' on the Replica server and will connect to the Hyper-V Replica
Broker in the next retry interval. (Virtual machine ID E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5)
Replication operation for virtual machine 'VM' failed. (Virtual machine ID
E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5) (Primary server: 'Host1', Replica server:
'Broker')
At line:1 char:1
+ Start-VMInitialReplication -VMName 'VM'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Start-VMInitialReplication],
   VirtualizationOperationFailedException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVMInitialReplicationCommand


Doing the same process through the failover cluster gui I get a similar error. Says the replication was enabled successfully however initial replication could not be started. And goes on to say Hyper-V could not find the virtual machine on the replica server.

Has this yet to be recognized as a bug in Windows Server 2019?

Viewing all articles
Browse latest Browse all 19461

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>