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
4 When you run a recovery plan, Site Recovery Manager shuts down the virtual machines on the
protected site, and activates the virtual machines on the recovery site according to the type of
replication that you use.
n
For datastore-based replication, Site Recovery Manager surfaces the raw storage on the recovery
site that contains the replicated virtual machines as a vCenter Server datastore.
Site Recovery Manager registers the recovered datastore with the ESXi host or cluster with which
the placeholder datastore is registered.
n
vSphere Replication powers on the copies of the virtual machines on the recovery site.
5 Site Recovery Manager sends a request to vCenter Server to swap the identity of the placeholder virtual
machines for the replicated virtual machines that have surfaced on the recovery site.
Select a Placeholder Datastore
If you use array-based protection groups or vSphere Replication protection groups, you must specify a
placeholder datastore on the recovery site for Site Recovery Manager to use to store placeholder virtual
machines.
You must configure a placeholder datastore on both sites in the pair to establish bidirectional protection and
to perform reprotect.
NOTE Site Recovery Manager does not create placeholder virtual machines for storage policy protection
groups. You do not need to select a placeholder datastore if you only use storage policy protection groups.
Prerequisites
n
Verify that you connected and paired the protected and recovery sites.
n
Placeholder datastores must meet certain criteria.
n
For clusters, the placeholder datastores must be visible to all of the hosts in the cluster.
n
You cannot select as placeholder datastores any datastores that are replicated by using array-based
replication.
n
Do not select as placeholder datastores any datastores that you use as the replication target
datastore for vSphere Replication.
Procedure
1 In the vSphere Web Client, click Site Recovery > Sites, and select a site.
2 On the Manage tab, click Placeholder Datastores.
3 Click the icon to configure a placeholder datastore.
4 Select a datastore to designate as the location for placeholder virtual machines on the local site, and
click OK.
Previously configured datastores appear but you cannot select them. If a datastore is replicated, but
Site Recovery Manager does not have an array manager for that datastore, the option to select the
replicated datastore might be available. Do not select replicated datastores that Site Recovery Manager
does not manage.
IMPORTANT If you use vSphere Replication, do not select a placeholder datastore that you already use
as the target datastore for replications. Selecting the same datastore for placeholder virtual machines as
you use to contain the replica virtual machines that vSphere Replication creates can cause problems
when you run reprotect.
Make sure placeholder datastores are not in the same Storage DRS cluster as the vSphere Replication
replica target datastores.
Chapter 4 About Placeholder Virtual Machines
VMware, Inc. 43