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
Figure 6‑1. SRM Failback Process
Replica
virtual
machines
power off
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
1. Planned Migration
Site A
Protected
virtual
machines
power off
Replica
virtual
machines
power on
Virtual machines replicate from site A to site B
Site B
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
Site A Site B
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
2. Reprotect–Recovery site becomes protected site
Direction of replication is reversed
Protected
virtual
machines
power on
Protected
virtual
machines
power on
Recovery site becomes
protected site
Protected site becomes
recovery site
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
Site A
Protected
virtual
machines
power off
Replica
virtual
machines
power on
Site B
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
3. Planned Migration
Migrate virtual machines from protected to recovery site
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
Site A
Replica
virtual
machines
power off
Protection and recovery sites and direction of replication
are restored to pre-migration condition
Site B
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
apps
OS
4. Reprotect again– original protected and
recovery site configuration restored
Perform a Failback
After SRM performs a recovery, you can perform a failback to restore the original configuration of the
protected and recovery sites.
To aid comprehension, the original protected site from before a recovery is site A. The original recovery site
is site B. After a recovery from site A to site B, the recovered virtual machines are running on site B without
protection.
Prerequisites
Verify that the following conditions are in place.
n
You have performed a recovery, either as part of a planned migration or as part of a disaster recovery.
n
The original protected site, site A, is running.
n
If you performed a disaster recovery, you must perform a planned migration recovery when the hosts
and datastores on the protected site, site A, are running again.
n
You did not run reprotect since the recovery.
Procedure
1 Click Recovery Plans in the SRM interface, select a recovery plan, and click Reprotect.
2 Select the check box to confirm that you understand that the reprotect operation is irreversible.
3 Review the reprotect information and click Start.
4 Monitor the reprotect operation on the Recovery Steps tab until it finishes.
Site Recovery Manager Administration
54 VMware, Inc.