MonitoringInterval : 12:00:00
MonitoringStartTime : 15:00:00
DefaultStorageLocation : C:\Replicas\
OperationalStatus : {Ok}
StatusDescriptions : {The Replication Service is fully
operational.}
AuthorizationEntries : {*}
Key :
IsDeleted : False
RepEnabled : True
KerbAuthPort : 80
CertAuthPort : 443
AllowAnyServer : True
AuthType : Kerb
Additionally, replication entries from specific hosts can be added by using the -New-
VMReplicationAuthorizationEntry cmdlet. Here’s an example:
New-VMReplicationAuthorizationEntry -AllowedPrimaryServer
-ReplicaStorageLocation
The final step to complete in order to have a server accept replication is to enable the
required firewall exception for the port used: 80 for HTTP and 443 for HTTPS. The
firewall exceptions are built into Windows Server but are not enabled even after
replication configuration is complete. Thus you will need to start the Windows
Firewall with the Advanced Security administrative tool, select Inbound Rules, and
enable either (depending on your authentication methods) Hyper-V Replica HTTP
Listener (TCP-In) or Hyper-V Replica HTTPS Listener (TCP-In), or both.
Once the replica server has been enabled for replication, it is important also to enable
the primary Hyper-V server as a replica. This allows the reversal of replication in the
event that the virtual machine is activated on the replica server and now needs to start
replicating to the server that was previously the primary but would now be considered
the replica.
One item that you do not need to configure as part of the replication configuration is
the network to use for the replication traffic. The assumption is that this technology is
used between datacenters and that there would be only one valid path between them;
therefore, Hyper-V Replica will automatically choose the correct network to use for
the replication traffic.
If you have existing Windows Server 2012 Hyper-V Replica environments to upgrade
to Windows Server 2012 R2, you must upgrade the replica Hyper-V server first. The
same logic applies when upgrading to Windows Server 2016; the replica server must
be updated to the 2016 version before the source.