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
Specify a Nonreplicated Datastore for Swap Files 80
Recovering Virtual Machines Across Multiple Hosts on the Recovery Site 81
Resize Virtual Machine Disk Files During Replication Using Replication Seeds 82
Resize Virtual Machine Disk Files During Replication Without Using Replication Seeds 82
Reconfigure SRM Settings 82
Change Local Site Settings 83
Change Logging Settings 83
Change Recovery Settings 85
Change Remote Site Settings 86
Change the Timeout for the Creation of Placeholder Virtual Machines 86
Change Storage Settings 86
Change Storage Provider Settings 87
Change vSphere Replication Settings 88
Modify Settings to Run Large SRM Environments 89
10
Troubleshooting SRM Administration 93
Limitations to Protection and Recovery of Virtual Machines 93
vSphere Replication Limitations 96
SRM Events and Alarms 96
How SRM Monitors Connections Between Sites 96
Configure SRM Alarms 97
SRM Events Reference 97
vSphere Replication Events and Alarms 106
Configure vSphere Replication Alarms 106
List of vSphere Replication Events 106
Collecting SRM Log Files 109
Collect SRM Log Files By Using the SRM Interface 109
Collect SRM Log Files Manually 110
Access the vSphere Replication Logs 112
Manually Access the vSphere Replication Logs 112
Resolve SRM Operational Issues 113
SRM Doubles the Number of Backslashes in the Command Line When Running Callouts 113
Powering on Many Virtual Machines Simultaneously on the Recovery Site Can Lead to Errors 114
LVM.enableResignature=1 Remains Set After a SRM Test Failover 114
Adding Virtual Machines to a Protection Group Fails with an Unresolved Devices Error 115
Configuring Protection fails with Placeholder Creation Error 115
Planned Migration Fails Because Host is in an Incorrect State 116
Recovery Fails with a Timeout Error During Network Customization for Some Virtual
Machines 116
Recovery Fails with Unavailable Host and Datastore Error 117
Reprotect Fails with a vSphere Replication Timeout Error 117
Recovery Plan Times Out While Waiting for VMware Tools 117
Reprotect Fails After Restarting vCenter Server 118
Rescanning Datastores Fails Because Storage Devices are Not Ready 118
Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared
VMFS Datastore on ESXi Server 5.0 119
Application Quiescing Changes to File System Quiescing During vMotion to an Older Host 120
Reconfigure Replication on Virtual Machines with No Datastore Mapping 120
Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores 121
Contents
VMware, Inc. 5