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
Cause
SRM does not check how snapshot volumes are presented to ESXi hosts. SRM does not support setting the
LVM.enableResignature flag to 0. If you set the flag from 1 to 0, a virtual machine outage might occur each
time you perform a test failover or an actual failover occurs.
Setting the LVM.enableResignature flag on ESXi hosts is a host-wide operation. When this flag is set to 1,
during the host rescan or the next host reboot, all snapshot LUNs that are visible to the ESXi host, and that
can be resignatured, are resignatured.
If snapshot volumes unrelated to SRM are forcefully mounted to ESXi hosts on the recovery site, these LUNs
are resignatured as part of a host rescan during a test failover or an actual failover process. As a result, all
the virtual machines in these volumes become inaccessible.
Solution
To prevent outages, make sure that no snapshot LUNs that are unrelated to SRM, and that are forcefully
mounted, are visible to ESXi hosts on the recovery site.
Adding Virtual Machines to a Protection Group Fails with an Unresolved
Devices Error
Adding virtual machines to a protection group fails with an error if you did not configure the appropriate
inventory mappings.
Problem
When you add a virtual machine to a protection group, you see the error Unable to protect VM 'virtual
machine name' due to unresolved devices.
Cause
You did not configure the inventory mappings to map the devices of the virtual machine on the protected
site to the corresponding devices on the recovery site.
Solution
Configure the inventory mappings as described in Site Recovery Manager Installation and Configuration.
Configuring Protection fails with Placeholder Creation Error
When you configure protection on multiple virtual machines, the configuration fails with a placeholder
creation error.
Problem
Configuring protection on a large number of virtual machines at the same time fails with either a
placeholder creation timeout error or a placeholder creation naming error:
n
Placeholder VM creation error:Operation timed out:300 seconds
n
Placeholder VM creation error:The name 'placeholder_name' already exists
This problem occurs when you configure protection in different ways:
n
You create a protection group that contains a datastore or datastores that contain a large number of
virtual machines.
n
You use the Protection Groups > Virtual Machines > Restore All option in the SRM interface on a large
number of virtual machines.
n
You use the SRM API to protect a large number of virtual machines manually.
Chapter 10 Troubleshooting SRM Administration
VMware, Inc. 115