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.
Well the vswp files are created when a machine reboots or vmotions, so there are 4GB files created whenever a machine reboots....But if the machine isn't paging memory to the swap file is the replication even affected?
Joerg - I think that answers it. I was wondering if the host would page some relevant data to the vswp file even if it wasn't in use by the guest, sort of priming it for use. If the host just created an empty file and isn't writing to it...well no harm done.
Origin3k
4 Operator
•
2.4K Posts
1
March 27th, 2013 15:00
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
Ed.Willson
1 Rookie
•
14 Posts
0
March 27th, 2013 15:00
Well the vswp files are created when a machine reboots or vmotions, so there are 4GB files created whenever a machine reboots....But if the machine isn't paging memory to the swap file is the replication even affected?
Ed.Willson
1 Rookie
•
14 Posts
0
March 27th, 2013 16:00
Joerg - I think that answers it. I was wondering if the host would page some relevant data to the vswp file even if it wasn't in use by the guest, sort of priming it for use. If the host just created an empty file and isn't writing to it...well no harm done.