5.5

2 Set the srmMaxBootShutdownOps setting.
Option Description
Option text box
Type srmMaxBootShutdownOps.
Value text box
Type the maximum number of boot shutdown operations, for example 32.
3 Click OK to save your changes.
4 Log into the SRM Server host.
5 Open the vmware-dr.xml file in a text editor.
You find the vmware-dr.xml file in the C:\Program Files\VMware\VMware vCenter Site Recovery
Manager\config folder.
6 Change the defaultMaxBootAndShutdownOpsPerCluster and defaultMaxBootAndShutdownOpsPerHost
settings in the vmware-dr.xml file:
<config>
...
<defaultMaxBootAndShutdownOpsPerCluster>24</defaultMaxBootAndShutdownOpsPerCluster>
<defaultMaxBootAndShutdownOpsPerHost>4</defaultMaxBootAndShutdownOpsPerHost>
...
</config>
7 Restart the SRM Server to apply the new settings.
8 Click Sites in the SRM interface, right-click the site on which to change settings, and select Advanced
Settings.
9 Select vrReplication and increase the synchronizationTimeout setting.
For example, increase the synchronizationTimeout value to 7200 seconds.
10 Select storage and increase the commandTimeout setting.
For example, increase the commandTimeout value to 3600 seconds.
11 Click OK to save your changes.
Settings for Large SRM Environments
To protect a large number of virtual machines, you can modify the default SRM settings to achieve the best
possible recovery times in your environment or to avoid timeouts.
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.
To modify the settings, see “Modify Settings to Run Large SRM Environments,” on page 89.
Site Recovery Manager Administration
90 VMware, Inc.