6.1
Table Of Contents
- Site Recovery Manager Administration
- Contents
- About VMware Site Recovery Manager Administration
- Updated Information
- Site Recovery Manager Privileges, Roles, and Permissions
- How Site Recovery Manager Handles Permissions
- Site Recovery Manager and the vCenter Server Administrator Role
- Site Recovery Manager and vSphere Replication Roles
- Managing Permissions in a Shared Recovery Site Configuration
- Assign Site Recovery Manager Roles and Permissions
- Site Recovery Manager Roles Reference
- Replicating Virtual Machines
- Configuring Mappings
- About Placeholder Virtual Machines
- Creating and Managing Protection Groups
- About Array-Based Replication Protection Groups and Datastore Groups
- About vSphere Replication Protection Groups
- About Storage Policy Protection Groups
- Create Protection Groups
- Organize Protection Groups in Folders
- Add or Remove Datastore Groups or Virtual Machines to or from a Protection Group
- Apply Inventory Mappings to All Members of a Protection Group
- Configure Inventory Mappings for an Individual Virtual Machine in a Protection Group
- Modifying the Settings of a Protected Virtual Machine
- Remove Protection from a Virtual Machine
- Protection Group Status Reference
- Virtual Machine Protection Status Reference
- Creating, Testing, and Running Site Recovery Manager Recovery Plans
- Testing a Recovery Plan
- Performing a Planned Migration or Disaster Recovery By Running a Recovery Plan
- Differences Between Testing and Running a Recovery Plan
- Performing Test Recovery of Virtual Machines Across Multiple Hosts on the Recovery Site
- Create, Test, and Run a Recovery Plan
- Export Recovery Plan Steps
- View and Export a Recovery Plan History
- Delete a Recovery Plan
- Recovery Plan Status Reference
- Configuring a Recovery Plan
- Recovery Plan Steps
- Creating Custom Recovery Steps
- Suspend Virtual Machines When a Recovery Plan Runs
- Specify the Recovery Priority of a Virtual Machine
- Configure Virtual Machine Dependencies
- Enable vSphere vMotion for Planned Migration
- Configure Virtual Machine Startup and Shutdown Options
- Limitations to Protection and Recovery of Virtual Machines
- Customizing IP Properties for Virtual Machines
- Reprotecting Virtual Machines After a Recovery
- How Site Recovery Manager Reprotects Virtual Machines with Array Based Replication
- How Site Recovery Manager Reprotects Virtual Machines with vSphere Replication
- How Site Recovery Manager Reprotects Virtual Machines with Storage Policy Protection
- Preconditions for Performing Reprotect
- Reprotect Virtual Machines
- Reprotect States
- Restoring the Pre-Recovery Site Configuration By Performing Failback
- Interoperability of Site Recovery Manager with Other Software
- Site Recovery Manager and vCenter Server
- Using Site Recovery Manager with VMware Virtual SAN Storage and vSphere Replication
- How Site Recovery Manager Interacts with DPM and DRS During Recovery
- How Site Recovery Manager Interacts with Storage DRS or Storage vMotion
- How Site Recovery Manager Interacts with vSphere High Availability
- How Site Recovery Manager Interacts with Stretched Storage
- Using Site Recovery Manager with VMware NSX
- Site Recovery Manager and vSphere PowerCLI
- Site Recovery Manager and vRealize Orchestrator
- Protecting Microsoft Cluster Server and Fault Tolerant Virtual Machines
- Using Site Recovery Manager with SIOC Datastores
- Using Site Recovery Manager with Admission Control Clusters
- Site Recovery Manager and Virtual Machines Attached to RDM Disk Devices
- Site Recovery Manager and Active Directory Domain Controllers
- Advanced Site Recovery Manager Configuration
- Reconfigure Site Recovery Manager Settings
- Change Connections Settings
- Change Site Recovery Manager History Report Collection Setting
- Change Local Site Settings
- Change Logging Settings
- Change Recovery Settings
- Change Remote Manager Settings
- Change Remote Site Settings
- Change Replication Settings
- Change SSO Setting
- Change Storage Settings
- Change ABR Storage Policy Setting
- Change Storage Provider Settings
- Change vSphere Replication Settings
- Modify Settings to Run Large Site Recovery Manager Environments
- Reconfigure Site Recovery Manager Settings
- Site Recovery Manager Events and Alarms
- Collecting Site Recovery Manager Log Files
- Troubleshooting Site Recovery Manager
- Site Recovery Manager Doubles the Number of Backslashes in the Command Line When Running Callouts
- Powering on Many Virtual Machines Simultaneously on the Recovery Site Can Lead to Errors
- LVM.enableResignature=1 Remains Set After a Site Recovery Manager Test Recovery
- Adding Virtual Machines to a Protection Group Fails with an Unresolved Devices Error
- Configuring Protection fails with Placeholder Creation Error
- Rapid Deletion and Recreation of Placeholders Fails
- Planned Migration Fails Because Host is in an Incorrect State
- Recovery Fails with a Timeout Error During Network Customization for Some Virtual Machines
- Recovery Fails with Unavailable Host and Datastore Error
- Reprotect Fails with a vSphere Replication Timeout Error
- Recovery Plan Times Out While Waiting for VMware Tools
- Synchronization Fails for vSphere Replication Protection Groups
- Rescanning Datastores Fails Because Storage Devices are Not Ready
- Recovery Sticks at 36% During Planned Migration
- Operations Fail with Error About a Nonreplicated Configuration File
- Index
Protection Groups
IMPORTANT Protection groups for stretched storage must be created as storage policy protection groups. You
must create and use storage profiles to protect and recover stretched storage devices.
n
Protection groups with stretched devices must have a preferred direction from the protected site to the
recovery site. The preferred direction must match the site preference that the array maintains for the
corresponding devices. If the array supports site preference, then the protected site must have the site
preference.
n
Stretched and nonstretched virtual machines and consistency groups can be in the same protection
groups and the same recovery plan.
n
The stretched virtual machines must be on a stretched datastore and must be powered on at the
protected site.
n
You cannot create two protection groups in opposite directions by using the same stretched device pair,
but you can place virtual machines on the stretched devices at the recovery site that correspond to
protected devices at the protected site. You cannot protect these virtual machines, but they are
automatically protected during the reprotect process.
Planned Migration
n
The Run Recovery Plan wizard has an option to use Cross vCenter Server vMotion to perform a
planned migration. If the option is selected, Cross vCenter Server vMotion is used for all protected,
powered-on virtual machines on the stretched storage at the protected site. If the option is not selected,
the regular recovery workflow is used for replicated LUNs, including stretched storage.
n
If Cross vCenter Server vMotion fails for any reason, the recovery plan stops at the "Migrating VMs"
step and does not continue. If you cannot resolve the problem that is preventing Site Recovery Manager
from using Cross vCenter Server vMotion, rerun the recovery plan with the vSphere vMotion option
turned off. The migration can then use the regular recovery workflow for replicated LUNs.
n
During the deactivate step the stretched devices stay mounted at the protected site even if vMotion is
not used. Site Recovery Manager ignores non-protected replica virtual machines on the stretched
devices at the protected site and does not unregister them.
Test Recovery
n
Test recovery is performed by using the regular test recovery workflow for replicated devices,
including stretched devices. vMotion compatibility checks are performed for each virtual machine on
the stretched devices.
n
If the array does not support creating read-write snapshots for stretched devices,
Site Recovery Manager does not allow you to perform a test recovery for these devices.
Cross vCenter Server vMotion
Cross vCenter Server vMotion is not supported for migration from a vSphere Distributed Switch port group
to a standard switch network. In this instance, attempting to Cross vCenter Server vMotion a virtual
machine results in these error messages.
n
Unable to find a host in the cluster <cluster-name> that is compatible with the
Cross vCenter Server vMotion of the virtual machine <vm-name> from the protection group <PG-
name>.
Site Recovery Manager Administration
126 VMware, Inc.