5.0

Table Of Contents
Customizing Site Recovery Manager 8
In its default configuration, SRM enables a number of simple recovery scenarios. Advanced users can customize
SRM to support a broader range of site recovery requirements.
The default protection and recovery capabilities of SRM can be appropriate for sites that have simple
configurations or recovery objectives. Sites that have more complex requirements, such as many virtual
machines, a variety of guest operating systems, and application-specific networking requirements, typically
need to modify the settings.
This chapter includes the following topics:
n
“Customizing a Recovery Plan,” on page 75
n
“Configure Protection for a Virtual Machine or Template,” on page 86
n
“Configure Resource Mappings for a Virtual Machine,” on page 87
n
“Configure SRM Alarms,” on page 88
n
“Working with Advanced Settings,” on page 88
Customizing a Recovery Plan
You can customize a recovery plan to run commands, display messages that require a response, and change
the recovery priority of protected virtual machines.
A simple recovery plan that specifies only a test network to which the recovered virtual machines connect and
response times that the test should expect can provide an effective way to test an SRM configuration, However,
you must customize most recovery plans intended for production use to suit specific needs. For example, a
recovery plan for an emergency at the protected site is likely to be different from a planned migration of services
from one site to another.
NOTE A recovery plan always reflects the current state of the protection groups that it recovers. If any members
of a protection group display problems (for example, a status other than OK), you must correct the problems
before you can make any changes to the recovery plan.
Recovery Plan Steps
A recovery plan runs a series of steps that must be done in a specific order. You cannot change the order or
purpose of the steps, but you can insert your own steps that display messages and run commands.
Recovery plan steps have several behaviors:
n
Some steps are executed during all recoveries.
n
Some steps are executed only during test recoveries.
VMware, Inc.
75