5.5

3 Modify the vSphere Replication settings.
Option Description
Allow vSphere Replication to
recover virtual machines that are
included in SRM recovery plans
independently of SRM
If you configure vSphere Replication on a virtual machine and include the
virtual machine in an SRM recovery plan, you cannot recover the virtual
machine by using vSphere Replication independently of SRM. To allow
vSphere Replication to recover virtual machines independently of SRM,
select the allowOtherSolutionTagInRecovery check box.
Keep older multiple point in time
(PIT) snapshots during recovery
If you configure vSphere Replication to take PIT snapshots of protected
virtual machines, SRM only recovers the most recent snapshot when you
perform a recovery. To recover older PIT snapshots during recovery, select
the preserveMpitImagesAsSnapshots check box.
Change the timeout period for
reverse replication during reprotect
operations
Type a new value in the reverseReplicationTimeout text box. Change this
value if you experience timeout errors when vSphere Replication reverses
replication during reprotect operations.
Change the timeout period for
vSphere Replication
synchronization operations
Type a new value in the synchronizationTimeout text box. Change this
value if you experience timeout errors when vSphere Replication
synchronizes virtual machines on the recovery site.
Change the default RPO setting for
replications
Type a new value in the vrReplication.timeDefault text box. The default
value is 240 minutes (4 hours). This value is selected when you configure
replications, but you can specify a different RPO in the Configure
Replication wizard when you configure replication for an individual
virtual machine or for a group of virtual machines.
4 Click OK to save your changes.
Modify Settings to Run Large SRM Environments
If you use SRM to test or recover a large number of virtual machines, you might need to modify the default
SRM settings to achieve the best possible recovery times in your environment or to avoid timeouts.
In large environments, SRM might simultaneously power on or power off large numbers of virtual
machines. Simultaneously powering on or powering off large numbers of virtual machines can create a
heavy load on the virtual infrastructure, which might lead to timeouts. You can modify certain SRM settings
to avoid timeouts, either by limiting the number of power on or power off operations that SRM performs
concurrently, or by increasing the timeout periods.
The limits that you set on power on or power off operations depend on how many concurrent power on or
power off operations your infrastructure can handle.
You modify certain options in the Advanced Settings menus in the vSphere Client or in the SRM client
plug-in. To modify other settings, you edit the vmware-dr.xml configuration file on the SRM Server. Always
modify settings by using the client menus when an option exists. If you modify settings, you must make the
same modifications on the SRM Server and vCenter Server instances on both the protected and recovery
sites.
For descriptions of the settings that you can change, see “Settings for Large SRM Environments,” on
page 90.
Procedure
1 Right-click a cluster in the vCenter Server Inventory and select Edit Settings > vSphere DRS >
Advanced Options.
Chapter 9 Advanced SRM Configuration
VMware, Inc. 89