5.5
Table Of Contents
- Site Recovery Manager Administration
- Contents
- About VMware vCenter Site Recovery Manager Administration
- SRM Privileges, Roles, and Permissions
- Replicating Virtual Machines
- How the Recovery Point Objective Affects Replication Scheduling
- Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
- Configure Replication for a Single Virtual Machine
- Configure Replication for Multiple Virtual Machines
- Replicate Virtual Machines By Using Replication Seeds
- Reconfigure Replications
- Stop Replicating a Virtual Machine
- Creating Protection Groups
- Creating, Testing, and Running 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
- How SRM Interacts with DPM and DRS During Recovery
- How SRM Interacts with Storage DRS or Storage vMotion
- How SRM Interacts with vSphere High Availability
- Protecting Microsoft Cluster Server and Fault Tolerant Virtual Machines
- Create, Test, and Run a Recovery Plan
- Export Recovery Plan Steps
- View and Export Recovery Plan History
- Cancel a Test or Recovery
- Delete a Recovery Plan
- Reprotecting Virtual Machines After a Recovery
- Restoring the Pre-Recovery Site Configuration By Performing Failback
- Customizing a Recovery Plan
- Recovery Plan Steps
- Specify the Recovery Priority of a Virtual Machine
- Creating Custom Recovery Steps
- Types of Custom Recovery Steps
- How SRM Handles Custom Recovery Steps
- Create Top-Level Command Steps
- Create Top-Level Message Prompt Steps
- Create Command Steps for Individual Virtual Machines
- Create Message Prompt Steps for Individual Virtual Machines
- Guidelines for Writing Command Steps
- Environment Variables for Command Steps
- Customize the Recovery of an Individual Virtual Machine
- Customizing IP Properties for Virtual Machines
- Advanced SRM Configuration
- Configure Protection for a Virtual Machine or Template
- Configure Resource Mappings for a Virtual Machine
- Specify a Nonreplicated Datastore for Swap Files
- Recovering Virtual Machines Across Multiple Hosts on the Recovery Site
- Resize Virtual Machine Disk Files During Replication Using Replication Seeds
- Resize Virtual Machine Disk Files During Replication Without Using Replication Seeds
- Reconfigure SRM Settings
- Change Local Site Settings
- Change Logging Settings
- Change Recovery Settings
- Change Remote Site Settings
- Change the Timeout for the Creation of Placeholder Virtual Machines
- Change Storage Settings
- Change Storage Provider Settings
- Change vSphere Replication Settings
- Modify Settings to Run Large SRM Environments
- Troubleshooting SRM Administration
- Limitations to Protection and Recovery of Virtual Machines
- SRM Events and Alarms
- vSphere Replication Events and Alarms
- Collecting SRM Log Files
- Access the vSphere Replication Logs
- Resolve SRM Operational Issues
- SRM 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 SRM Test Failover
- Adding Virtual Machines to a Protection Group Fails with an Unresolved Devices Error
- Configuring Protection fails with Placeholder Creation Error
- 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
- Reprotect Fails After Restarting vCenter Server
- Rescanning Datastores Fails Because Storage Devices are Not Ready
- Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared VMFS Datastore on ESXi Server 5.0
- Application Quiescing Changes to File System Quiescing During vMotion to an Older Host
- Reconfigure Replication on Virtual Machines with No Datastore Mapping
- Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores
- vSphere Replication RPO Violations
- vSphere Replication Does Not Start After Moving the Host
- Unexpected vSphere Replication Failure Results in a Generic Error
- Generating Support Bundles Disrupts vSphere Replication Recovery
- Recovery Plan Times Out While Waiting for VMware Tools
- Index
n
Two virtual machines share a raw disk mapping (RDM) device on a SAN array, as in the case of a
Microsoft cluster server (MSCS) cluster.
n
Two datastores span extents corresponding to different partitions of the same device.
n
A single datastore spans two extents corresponding to partitions of two different devices. The two
extents must be in a single consistency group and the SRA must report consistency group information
from the array in the device discovery stage. Otherwise, the creation of protection groups based on this
datastore is not possible even though the SRA reports that the extents that make up this datastore are
replicated.
n
Multiple datastores belong to a consistency group. A consistency group is a collection of replicated
datastores where every state of the target set of datastores existed at a specific time as the state of the
source set of datastores. Informally, the datastores are replicated together such that when recovery
happens using those datastores, software accessing the targets does not see the data in a state that the
software is not prepared to deal with.
Protecting Virtual Machines on VMFS Datastores that Span Multiple LUNs or
Extents
Not all SRAs report consistency group information from the storage array, because not all storage arrays
support consistency groups. If an SRA reports consistency group information from the array following a
datastore discovery command, the LUNs that constitute a multi-extent VMFS datastore must be in the same
storage array consistency group. If the array does not support consistency groups and the SRA does not
report any consistency group information, SRM cannot protect virtual machines located on on the multi-
extent datastore.
Create Array-Based Protection Groups
You create array-based protection groups to enable the protection of virtual machines in datastore groups
that you configure to use array-based replication.
SRM computes the datastore groups when you configure the array pair or when you refresh the list of
devices.
After you create a protection group, SRM creates placeholder virtual machines and applies inventory
mappings for each virtual machine in the group. If SRM cannot map a virtual machine to a folder, network,
and resource pool on the recovery site, SRM sets the virtual machine in the Mapping Missing status, and
does not create a placeholder for it.
You can organize protection groups in folders. Different views in the Recovery interface display the names
of the protection groups, but they do not display the folder names. If you have two protection groups with
the same name in different folders, it might be difficult to tell them apart in some views in the Recovery
interface. Consequently, ensure that protection group names are unique across all folders. In environments
in which not all users have view privileges for all folders, to be sure of the uniqueness of protection group
names, do not place protection groups in folders.
When you create protection groups, wait to ensure that the operations finish as expected. Make sure that
SRM creates the protection group and that the protection of the virtual machines in the group is successful.
Procedure
1 Click Protection Groups in the SRM interface, and click Create Protection Group.
2 On the Select a Site and Protection Group Type page, select which site to protect and select Array Based
Replication.
3 Select an array pair, and click Next.
Chapter 3 Creating Protection Groups
VMware, Inc. 31