6.1

Table Of Contents
n
DRS rules that you set on the protected site are not transferred to the recovery site after a recovery. For
this reason, you must set the DRS rules on the placeholder virtual machines on the recovery site.
n
Do not run a test recovery or a real recovery before you set the DRS rules on the recovery site.
If you do not follow the guidelines on either the protected site or on the recovery site, vSphere vMotion
might move MSCS virtual machines to a configuration that Site Recovery Manager does not support.
n
In a cluster-in-a-box deployment on either the protected or recovery site, vSphere vMotion might move
MSCS virtual machines to different ESXi hosts.
n
In a cluster-in-a-box deployment on either the protected or recovery site, vSphere vMotion might move
some or all of the MSCS virtual machines to a single ESXi host.
Using Site Recovery Manager with SIOC Datastores
Site Recovery Manager fully supports storage I/O control (SIOC).
Planned Migration of Virtual Machines on Datastores that Use SIOC
In previous releases of Site Recovery Manager you had to disable storage I/O control (SIOC) on datastores
that you included in a recovery plan before you ran a planned migration. This release of
Site Recovery Manager fully supports SIOC, so you do not have to disable SIOC before you run a planned
migration.
Disaster Recovery and Reprotect of Virtual Machines on Datastores that Use
SIOC
In previous releases of Site Recovery Manager, if you ran a disaster recovery with SIOC enabled, the
recovery would succeed with errors. After the recovery, you had to manually disable SIOC on the protected
site and run a planned migration recovery again. You could not run reprotect until you successfully ran a
planned migration. This release of Site Recovery Manager fully supports SIOC, so recovery succeeds
without errors and you can run planned migration and reprotect after a disaster recovery without disabling
SIOC.
Using Site Recovery Manager with Admission Control Clusters
You can use Admission Control on a cluster to reserve resources on the recovery site.
However, using Admission Control can affect disaster recovery by preventing Site Recovery Manager from
powering on virtual machines when running a recovery plan. Admission Control can prevent virtual
machines from powering on if powering them on would violate the relevant Admission Control constraints.
You can add a command step to a recovery plan to run a PowerCLI script that disables Admission Control
during the recovery. See “Creating Custom Recovery Steps,” on page 82 for information about creating
command steps.
1 Create a pre-power on command step in the recovery plan that runs a PowerCLI script to disable
Admission Control.
Get-Cluster cluster_name | Set-Cluster -HAAdmissionControlEnabled:$false
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.
Chapter 11 Interoperability of Site Recovery Manager with Other Software
VMware, Inc. 131