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
Procedure
1 Click Recovery Plans in the left pane, select the recovery plan to run, and click Recovery.
2 Review the information in the confirmation prompt, and select I understand that this process will
permanently alter the virtual machines and infrastructure of both the protected and recovery
datacenters.
3 Select the type of recovery to run.
Option Description
Planned Migration
Recovers virtual machines to the recovery site when both sites are running.
If errors occur on the protected site during a planned migration, the
planned migration operation fails.
Disaster Recovery
Recovers virtual machines to the recovery site if the protected site
experiences a problem. If errors occur on the protected site during a
disaster recovery, the disaster recovery continues and does not fail.
4 (Optional) Select the Forced Recovery - recovery site operations only check box.
This option is available if you selected Disaster Recovery and you enabled the forced recovery function.
5 Click Next.
6 Review the recovery information and click Start.
7 Click the Recovery Steps tab.
The Recovery Steps tab displays the progress of individual steps. The Recent Tasks area reports the
progress of the overall plan.
Recover a Point-in-Time Snapshot of a Virtual Machine
With vSphere Replication, you can retain point-in-time snapshots of a virtual machine. You can configure
SRM to recover a number of point-in-time snapshots of a virtual machine when you run a recovery plan.
You configure the retention of point-in-time snapshots when you configure vSphere Replication on a virtual
machine. For more information about point-in-time snapshots, see “Replicating a Virtual Machine and
Enabling Multiple Point in Time Instances,” on page 22.
NOTE You cannot use the SRM interface to configure replication that uses point in time (PIT) snapshots. To
enable PIT snapshots, configure replication of a virtual machine by using the vSphere Web Client. See
Configure Replication for a Single Virtual Machine in vSphere Replication Administration.
SRM only recovers the most recent PIT snapshot during a recovery. To recover older snapshots, you must
enable the vrReplication > preserveMpitImagesAsSnapshots option in Advanced Settings in the SRM
interface. See “Change vSphere Replication Settings,” on page 88.
Point-in-time recovery is not available with array-based replication.
Procedure
1 Configure SRM to retain older point-in-time snapshots by setting the vrReplication >
preserveMpitImagesAsSnapshots option.
2 Use the vSphere Web Client to configure replication of a virtual machine, selecting the option to retain a
number of point-in-time snapshots.
3 In the SRM interface, add the virtual machine to a vSphere Replication protection group.
4 Include the vSphere Replication protection group in a recovery plan.
Site Recovery Manager Administration
46 VMware, Inc.