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
Table 10‑2. Protection Group Replication Informational Events (Continued)
Event Key Event Description Cause
PlaceholderVmCreatedEvent The placeholder virtual machine was
created in the VMware vCenter
Server inventory.
Posted on the Recovery site vCenter
Server only when we create the
placeholder virtual machine as a result
of protection, repair.
PlaceholderVmCreatedFromOldProd
uctionVmEvent
The placeholder virtual machine was
created in the VMware vCenter
Server inventory using the identity of
the old protected virtual machine.
Posted on the Recovery site vCenter
Server only when we create the
placeholder virtual machine as a result
of swapping for the old protected
virtual machine during or after
reprotect.
Table 10‑3. Protection Group Replication Warning Events
Event Key Event Description Cause
VmNotFullyProtectedEvent Virtual machine in group: One or
more devices need to be configured
for protection.
Posted on the protected site vCenter
Server only upon device handling
updating the recovery location settings
with a non-empty unresolvedDevices
set. This can be triggered by changes to
the protected virtual machine or
during reprotect of a virtual machine.
PlaceholderVmUnexpectedlyDeleted
Event
Virtual machine in group: The
placeholder virtual machine was
removed from the VMware vCenter
Server inventory.
Posted on the Recovery site vCenter
Server only when we detect that the
placeholder virtual machine was
unexpectedly deleted or removed from
the vCenter inventory.
Table 10‑4. Protection Group Replication Error Events
Event Key Event Description Cause
ProductionVmDeletedEvent Virtual machine in group: The
protected virtual machine has been
removed from the virtual
machineware vCenter Server
inventory.
Posted when we detect that the
protected virtual machine’s protected
virtual machine has been deleted or
removed from the vCenter inventory.
ProductionVmInvalidEvent Virtual machine in group: Cannot
resolve the file locations of the
protected virtual machine for
replication.
Posted whenever we handle device or
recovery location changes but notice
that the provider cannot find the
protected virtual machine files in order
to replicate them.
Chapter 10 Troubleshooting SRM Administration
VMware, Inc. 99