which is different from a Live Migration operation.Figure 8. 8 Performing a planned failoverUnplanned Failover (Failover) This is triggered on the replica virtual machine
because the assumption is that the failover was not planned, and the primary is not
available because a disaster has occurred. When this is performed, a replication of
pending changes is not possible, and reverse replication has to be manually
enabled with a resynchronization required because there is no way to know where
the primary and the replica stopped replicating. When starting the reverse
replication, choose Do Not Copy The Initial Replication on the Initial Replication
page. The VM on the original primary VM can be used, and a block-by-block
comparison will be performed to synchronize between the replica VM and the
original primary VM. Only the delta content needs to be sent over the network.
When performing an unplanned failover, an option to select the point in time is
available in the same way as for the test failover.In Windows Server 2012 , if the option to maintain periodic snapshots of the primary
virtual machine was enabled with Hyper-V Replica, then the replica virtual machine
would show those point-in-time snapshots in the Snapshots view. This is no longer
the case in Windows Server 2012 R 2 and above Hyper-V, which may initially lead you
to believe that the snapshots are not being maintained for the replica, which is not the
case. The various points in time are available and listed when performing a failover
with Hyper-V Replica, as previously discussed. You can also see this using PowerShell,
as shown here:
PS C:> Get‐VMSnapshot savdalapp 01
VMName Name SnapshotType
CreationTime
——— —— —————— ——————