System information

Because of the significant effect that running a recovery has on the protected and recovery sites, you cannot
use the vCenter Orchestrator plug-in for vCenter Site Recovery Manager to automate test recovery, planned
migration, or disaster recovery. Recovery is too sensitive to automate and always requires human
intervention.
The vCenter Orchestrator plug-in for vCenter Site Recovery Manager includes vCenter Orchestrator actions,
workflows, policy templates to trigger actions when certain events occur, and scripting objects to expose
selected elements of the Site Recovery Manager API to workflows.
n
The plug-in provides actions and workflows that create a Site Recovery Manager infrastructure:
n
Create array-based protection groups and vSphere Replication protection groups
n
Create inventory mappings between matching objects
n
Add protection groups to existing recovery plans
n
The plug-in provides actions and workflows that protect virtual machines:
n
Protect a virtual machine by using an existing array-based protection group
n
Protect a virtual machine by using an existing vSphere Replication protection group
n
The plug-in provides actions and workflows that configure recovery settings on virtual machines:
n
Set the recovery priority
n
Create per-virtual machine recovery steps
n
Set the final power state of a recovered virtual machine
n
The plug-in provides actions and workflows that obtain information from
Site Recovery Manager Server:
n
List protected datastores
n
List protection groups and recovery plans
n
Find array-based protection groups by datastore
n
Get unassigned replication datastores and recovery plan states
Protecting Microsoft Cluster Server and Fault Tolerant Virtual
Machines
You can use Site Recovery Manager to protect Microsoft Cluster Server (MSCS) and fault tolerant virtual
machines, with certain limitations.
To use Site Recovery Manager to protect MSCS and fault tolerant virtual machines, you might need to
change your environment.
General Limitations to Protecting MSCS and Fault Tolerant Virtual Machines
Protecting MSCS and fault tolerant virtual machines is subject to the following limitations.
n
You can use array-based replication only to protect MSCS virtual machines. Protecting MSCS virtual
machines with vSphere Replication is not supported.
n
Reprotect of MSCS or fault tolerant virtual machines requires VMware High Availability (HA) and
VMware Distributed Resource Scheduler (DRS). When you move MSCS or fault tolerant virtual
machines across their primary and secondary sites during reprotect, you must enable HA and DRS, and
set the affinity and antiaffinity rules as appropriate. See “DRS Requirements for Protection of MSCS
Virtual Machines,” on page 97.
n
vSphere does not support vSphere vMotion for MSCS virtual machines.
Site Recovery Manager Administration
96 VMware, Inc.