5.5

Procedure
1 In the vSphere Client, right-click an ESXi cluster and click Edit Settings.
2 In the Settings page for the cluster, click Swapfile Location, select Store the swapfile in the datastore
specified by the host, and click OK.
3 For each host in the cluster, select a nonreplicated datastore.
a Select a host and click the Configuration tab.
b In the Software panel, click Virtual Machine Swapfile Location, and click Edit at the top right of
the main panel.
c On the Virtual Machine Swapfile Location page, select a nonreplicated datastore and click OK.
4 For standalone hosts that are not part of a cluster, select the host and click the Configuration tab.
5 In the Software panel, click Virtual Machine Swapfile Location, and click Edit at the top right of the
main panel.
6 Select Store the swapfile in a swapfile datastore selected below, select the datastore, and click OK.
7 Power off and power on all of the virtual machines in the cluster.
Resetting the guest operating system is not sufficient. The change of swapfile location takes effect after
you power off then power on the virtual machines.
8 Browse the datastore that you selected for swapfiles and verify that VSWP files are present for the
virtual machines in the cluster.
Recovering Virtual Machines Across Multiple Hosts on the Recovery
Site
You can create recovery plans that recover virtual machines across multiple recovery site hosts in a
quarantined test network.
With SRM, the vSwitches can be DVS based and span hosts. If you accept the default test network
configured as Auto, then virtual machines that are recovered across hosts are placed in their own test
network. Each test switch is isolated between hosts. As a result, virtual machines in the same plan are
isolated when the recovery finishes. To allow the virtual machines to communicate, establish and select DVS
switches or VLANs. With an isolated VLAN that connects all hosts to each other but not to a production
network, you can more realistically test a recovery. To achieve connectivity among recovery hosts, but
maintain isolation from the production network, follow these recommendations:
n
Create DVS switches that are connected to an isolated VLAN that is private. Such a VLAN allows hosts
and virtual machines to be connected, but to be isolated from production virtual machines. Use a
naming convention that clearly designates that the DVS is for testing use, and select this DVS in the
recovery plan test network column in the recovery plan editor.
n
Create test VLANs on a physical network, providing no route back to the protected site. Trunk test
VLANs to recovery site vSphere clusters and create virtual switches for test VLAN IDs. Use a clear
naming convention to identify that these switches are for testing. Select these switches from the test
recovery network column in the recovery plan editor.
Chapter 9 Advanced SRM Configuration
VMware, Inc. 81