The *.vswp is created when you turn on a VM. As long as your HOST doesnt run out of memory and TPS, Balloning, Compression cant free any memory nothing is written into the *.vswp.  Without any changes there your replication isnt effected. If you set the memory resevertion to 100% no *.vswp is created. Maybe you referer to the pagefile of the GuestOS? Yes, i have seen that ppl create a extra vDISK for it and store the VMDK on a datastore->volume which isnt part of the replication. But that may cause trouble when ever you have a real need your replicated data because starting a VM with a GuestOS which doesnt have a pagefile can effect the application. Its not easy to start a java based app without configurated swapfile. Regards, Joerg
Hi - I'm trying to reduce the amount of data that is getting replicated, I'm running out of bandwidth. I'm trying to figure out if moving the vswp files to another non-replicated lun will help. Memory is not overcommited, so the machines shouldn't be using this file. But what I'm wondering is if the hosts are updating the file without the guest using it...   Thanks,       Ed
Replication and vswp files