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
Advanced SRM Configuration 9
The SRM default configuration enables some simple recovery scenarios. Advanced users can customize
SRM to support a broader range of site recovery requirements.
This chapter includes the following topics:
n
“Configure Protection for a Virtual Machine or Template,” on page 79
n
“Configure Resource Mappings for a Virtual Machine,” on page 80
n
“Specify a Nonreplicated Datastore for Swap Files,” on page 80
n
“Recovering Virtual Machines Across Multiple Hosts on the Recovery Site,” on page 81
n
“Resize Virtual Machine Disk Files During Replication Using Replication Seeds,” on page 82
n
“Resize Virtual Machine Disk Files During Replication Without Using Replication Seeds,” on
page 82
n
“Reconfigure SRM Settings,” on page 82
Configure Protection for a Virtual Machine or Template
You can edit the protection properties of any virtual machine or template in a protection group. You can
change the resource mappings, attached storage devices and their datastores, and other properties that
control the configuration with which SRM recovers the virtual machine.
You must configure protection for virtual machines that have a status of Not Configured or Mapping
Missing.
If you are using array-based replication, editing the properties of a virtual machine to add or change storage
devices, such as hard disks or DVD drives, can affect the protection of that machine if the device that you
add is stored on a datastore that is not replicated, or that is protected by a different protection group.
n
If the new device is created on a replicated datastore that is not part of any protection group, the
datastore is added to the virtual machine's protected datastore group and the protection of the virtual
machine is unaffected.
n
If the new device is created on a replicated datastore that is protected by a different protection group,
this invalidates the protection of the virtual machine.
n
If the new device is created on a nonreplicated datastore, this invalidates the protection of the virtual
machine.
n
If you use Storage vMotion to move a virtual machine to a nonreplicated datastore, or to a replicated
datastore on an array that SRM has not been configured to manage (through an SRA), this invalidates
the protection of the virtual machine. You can use Storage vMotion to move a virtual machine to
datastore that is part of another protection group.
VMware, Inc.
79