5.5

2 Create a post-power on command step in the recovery plan to reenable Admission Control after the
virtual machine powers on.
Get-Cluster cluster_name | Set-Cluster -HAAdmissionControlEnabled:$true
If you disable Admission Control during recovery, you must manually reenable Admission Control after
you perform cleanup following a test recovery. Disabling Admission Control might affect the ability of High
Availability to restart virtual machines on the recovery site. Do not disable Admission Control for
prolonged periods.
vSphere Replication Limitations
vSphere Replication is subject to some limitations when replicating virtual machines.
Replicating Large Volumes
vSphere Replication can replicate virtual machines greater than 2TB with the following limitations:
n
If you move a virtual machine with replicated disks over 2032GB back to a machine on an older release,
vSphere Replication cannot replicate or power on the virtual machine.
n
Full sync of very large disks can take days.
n
vSphere Replication must track changed blocks and consumes more memory on larger disks.
n
vSphere Replication tracks larger blocks on disks over 2TB. Replication performance on a disk over 2TB
might be different on a disk over 2TB for the same workload depending on how much of the disk goes
over the network for a particular set of changed blocks.
n
Replication might consume more or less bandwidth depending on the workload and how it changes
blocks on the disk during the RPO interval.
Shared Disk Support
vSphere Replication cannot replicate virtual machines that share vmdk files in this release.
SRM Events and Alarms
SRM supports event logging. Each event includes a corresponding alarm that SRM can trigger if the event
occurs. This provides a way to track the health of your system and to resolve potential issues before they
affect the protection that SRM provides.
How SRM Monitors Connections Between Sites
SRM monitors the connection between the protected and recovery sites and logs events if the remote site
stops responding.
When SRM establishes the connection between two paired SRM Server instances, the SRM Server that
initiated the connection sends a RemoteSiteUpEvent.
If SRM detects that a monitored connection has broken, it starts periodic connection checks by sending a
ping request to the remote site. SRM monitors the connection checks and logs events.
n
SRM sends pings at regular intervals. You can configure this interval by setting the
remoteSiteStatus.pingInterval value. The default is five minutes.
n
The connection monitor skips a number of failed pings. You can configure this number by setting the
remoteSiteStatus.pingFailedDelay value.
n
When the number of skipped failed pings exceeds the value of the remoteSiteStatus.pingFailedDelay
setting, SRM sends a RemoteSitePingFailedEvent event.
Site Recovery Manager Administration
96 VMware, Inc.