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‑5. Recovery Events (Continued)
Event Key Event Description Cause
RecoveryPlanServerCommandBegin
Recovery Plan has started to run a
Command on the SRM Server
machine.
Signaled on the recovery site when
SRM has started to run a Callout
Command on the SRM Server
machine.
RecoveryPlanServerCommandEnd
Recovery Plan has completed the
execution of a Command on the
SRM Server machine.
Signaled on the recovery site when
SRM has finished running a Callout
Command on the SRM Server
machine.
RecoveryPlanVmCommandBegin
Recovery Plan has started to run a
Command on a recovered virtual
machine.
Signaled on the recovery site when
SRM has started to run a Callout
Command on a recovered virtual
machine.
RecoveryPlanVmCommandEnd
Recovery Plan has completed the
execution of a Command on a
recovered virtual machine.
Signaled on the recovery site when
SRM has finished running a Callout
Command on a recovered virtual
machine.
Storage and Storage Provider Events
Storage and storage provider events provide information about actions and status related storage or storage
providers.
Table 10‑6. SRA Events
Type Description Content
StorageAdapterLoaded
Loaded the specified SRA. SRM detected new SRA either during
startup or during user-initiated SRAs
reload.
StorageAdapterReloadFailed
Failed to load SRA from the specified
path.
SRM failed to reload previously
known SRA either during startup or
during user-initiated SRAs reload.
StorageAdapterChanged
Loaded new version of the specified
SRA.
SRM detected that previously known
SRA was upgraded.
Table 10‑7. Array Manager Events
Type Description Content
StorageArrayManagerAdded
Created the specified array manager
using the specified SRA.
User added an Array Manager.
StorageArrayManagerRemoved
Deleted the specified array manager. User removed an Array Manager.
StorageArrayManagerReconfigured
Reconfigured the specified array
manager.
User edited Array Manager properties.
StorageArrayManagerPingOk
Ping for the specified array manager
succeeded.
SRM Server successfully pinged an
Array Manager.
StorageArrayManagerPingFailed
Failed to ping the specified array
manager.
An error occurred during Array
Manager ping.
Chapter 10 Troubleshooting SRM Administration
VMware, Inc. 101