Avoiding replication of paging files and other transient data in Site Recovery Manager (2009324)
Specify a nonreplicated datastore for swapfiles
Create a nonreplicated virtual disk for paging file storage
Specifying a nonreplicated datastore for swapfiles
In the vSphere Client, right-click an ESX/ESXi cluster and click Edit Settings.
In the Settings window for the cluster, click Swapfile Location, select Store the swapfile in the datastore specified by the host, and then click OK.
- For each host in the cluster, select a nonreplicated datastore.
- Click the Configuration tab.
- On the Swapfile Location line, click Edit.
- In the Virtual Machine Swapfile Location window, select a nonreplicated datastore and click OK.
Creating a nonreplicated virtual disk for paging file storage
You can avoid replication of a virtual machine's Windows paging file by creating a virtual disk on a nonreplicated datastore, configuring Windows to create its paging file on that disk, and configuring a nonreplicated copy of that disk at the recovery site.
At the protected site, select a nonessential virtual machine (one that you can power off during this procedure) or create a temporary virtual machine for this purpose.
Because of differences in the NTFS file system among Windows releases, you must perform this procedure for each version of Windows that the protection group includes.
Power off the selected virtual machine and add a new disk to it.
Create the disk file on a nonreplicated datastore at the protected site in a location where you typically store virtual machine templates. This disk becomes the template for all nonreplicated paging file disks. Create it with adequate capacity for a typical Windows paging file.
Power on the selected virtual machine and then create and format a partition on the new disk.
Configure the virtual machine to create its paging file on the new disk.
Power off the virtual machine and disconnect the new disk from it.
You can clone this disk to provide nonreplicated paging file storage for the other virtual machines.
To make the template available for cloning at the recovery site, copy it to a folder in a nonreplicated datastore at the recovery site.
You must copy the .vmdk file and its flat counterpart, for example, pagedisk.vmdk and pagediskflat.vmdk.
At the recovery site, use the vmkfstools command to create a clone of the copied disk.
Create one clone for every placeholder virtual machine, but do not attach any clones to a virtual machine. The clones are assigned as part of the protection configuration process and are attached during recovery.
At the protected site, configure each protected virtual machine.
Use the vmkfstools command to clone the disk.
Create the clone on a nonreplicated datastore at the protected site, and then copy it to a nonreplicated datastore at the recovery site with the original .vmdk file.
Connect the cloned disk to the virtual machine and then power on the virtual machine and assign a drive to the cloned disk.
Configure the virtual machine to create its paging file on the cloned disk.
Power off and then power on the virtual machine, so that it writes its paging file to the new location on the cloned disk.
At this point, the protected virtual machine is writing its paging file to a disk on a nonreplicated datastore at the protected site. Until you specify a recovery site location for this disk, the virtual machine does not have a valid protection configuration.
Assign recovery site storage for the paging file disk to one of the clones that you copied from the protected site. For more information, see the Configure Protection for a Virtual Machine or Template section of the VMware vCenter Site Recovery Manager 5.8 Administration Guide.
Initially, the paging file disk has a Recovery Location that is Not Configured. Click Browse, and then browse to the cloned vmdk file at the recovery site.
After you have configured the virtual machine to use the nonreplicated disk at the recovery site, SRM considers the virtual machine’s storage as properly configured and returns it to the protection group.
Failed to resolve file locator for backing of device 2001: (dr.storageProvider.fault.ResolvedVmFileNotFound)
For SRM 5.8.0, the workaround is to make a top-level folder for swap files and then specify the path for the each of the protected and recovery swap files for this virtual machine with this folder name prepended. For example, use:
instead of:[DSS_DRLinuxSwap] folder1/ITROMSPV11_SWAP.vmdk
To be alerted when this article is updated, click Subscribe to Document in the Actions box.[DSS_DRLinuxSwap] ITROMSPV11_SWAP.vmdk