For virtual machines that have virtual swap files located on datastores that are not replicated, you must configure the virtual machine to point to a different virtual swap file at the recovery site.
To configure the recovery site to use the proper swap file:
Caution: Shutdown the virtual machine and make backups of the .vmx file of the virtual machine before proceeding with these steps.
-
Verify that the virtual swap file for this virtual machine is not on datastores (or SAN LUNs) that are being replicated. If virtual swap file is on a datastore that is being replicated, no action is required.
If the .vmx file points to UUID and not a datastore name or relative path, proceed to the following step.
-
Ensure that the name of the datastore that contains the swap file is the same at the production and recovery sites.
-
Edit the .vmx file to point to the location of the datastore where the swap file is located.
To edit the .vmx file:
-
Open the .vmx file in text editor.
-
Add or edit the setting sched.swap.dir to point to the correct datastore.
For example:
sched.swap.dir = "/vmfs/volumes/swap_directory_name"
-
Remove any references to the sched.swap.derivedName setting. This is regenerated when the virtual machine is powered on.
-
Save your changes and close the file.
-
Power on the virtual machine.
-
Verify using the Datastore Browser or the Service Console that a virtual swap file is created in the new datastore for the virtual machine:
# ls /vmfs/volumes/swap_directory_name
The output appears similar to:
vm.vswp
-
Verify this at the recovery site.
If more information or assistance with this procedure is required file a support request with VMware Technical Support and note this KB Article ID in the problem description. For more information, see "How to Submit a Support Request" .