Hyper-V Replication State Stuck on "Waiting for Initial Replication" after Shared Nothing Live Migration – BUG or Real?

We have VMs that are replicating to Azure Site Recovery without issue.

One of those VMs was migrated (from 2012R2 host) over to a new Windows Server 2016 Hyper-V host that had the latest ASR agent installed.

In Hyper-V Manager, Replication shows normal. There are no errors in the Replication Health.

Everything appears normal and good on the Azure side as well.

However, if we run the PowerShell cmdlet Get-VM, it shows the replication state as "Waiting for Initial Replication"

Is this a bug or a real issue?

Read full post . . . .

"Cluster Rolling Upgrade" 2012R2 to 2016 ON NEW HOSTS?

Can the CRU process also be used if instead of reloading existing hosts, a new host with new hardware is instead used?

In the past there was always that CPU compatibility setting that needed to be checked for live migrations, but has that requirement changed now for mixed mode clusters?

Read full post . . . .

Go Que Newsroom