4.1

Change Remote Site Settings
Use the Advanced Settings remoteSiteStatus page to modify default values that the SRM server at the site to
which the vSphere client is currently connected uses to determine whether the SRM server at the remote site
is available
SRM monitors the
connection between the members of an SRM site pair (a protected site and its recovery site)
and, by default, raises alarms when this connection is interrupted. You can change the criteria that cause a
"remote site down" event and also change the way the related alarms are raised to suit the needs of your
installation and administrative staff.
Procedure
1 Right-click Site Recovery in the vSphere Client navigation pane and click Advanced Settings.
2 In the navigation pane of the Advanced Settings window, click remoteSiteStatus.
3 Modify settings as needed.
n
To change the interval at which SRM checks to see whether the SRM server at the remote site is
available, enter a new value in the remoteSiteStatus.checkInterval field.
n
To change the number of failed remote site status checks required to trigger a Remote Site Down
alarm, enter a new value in the remoteSiteStatus.panicDelay field.
n
To change the interval between Remote Site Down alarms, enter a new value in the
remoteSiteStatus.panicRepeatDelay field.
n
To change the number of remote site status checks to try before declaring the check a failure, enter a
new value in the remoteSiteStatus.warningDelay field.
4 Click OK to save your changes and close the Advanced Settings window.
Avoiding Replication of Paging Files and Other Transient Data
While SRM allows you to replicate transient data such as Windows paging files or virtual machine swapfiles,
such data need not be replicated. Preventing replication of such data avoids unnecessary consumption of
network bandwidth.
In the default configuration, virtual machines that use replicated datastores have all of their storage replicated,
including swap and paging files for which replication is unnecessary. These files, even if replicated, are
overwritten when a recovered virtual machine is powered on. While it does no harm to place them on a
replicated datastore, doing so adds unnecessary load to your replication infrastructure.
You can configure protected virtual machines to use local (nonreplicated) storage for swapfiles, Windows
paging files, or both.
Specify a Nonreplicated Datastore for Swapfiles
Every virtual machine requires a swapfile, which is normally created in the same datastore as the other virtual
machine files. When you use SRM, this datastore is replicated. To prevent swapfiles from being replicated,
create them on a nonreplicated datastore.
If you are using a nonreplicated datastore for swapfiles, you must create a nonreplicated datastore for all
protected clusters at both the protected and recovery sites. For more information, see the vSphere
documentation.
Site Recovery Manager Administration Guide
62 VMware, Inc.