i think what you are getting at is the swapfile policy for virtual machines. The default is in the same directory as the virtual machines. The second option is to store the swapfile in a datstore specified by host. A big black warning tells you that a host specified datastore may degrade vmotion performance for the affected virtual machines.
-Mike Original Message: ----------------- From: Joseph L. Casale [EMAIL PROTECTED] Date: Mon, 25 Aug 2008 12:29:36 -0600 To: ntsysadmin@lyris.sunbelt-software.com Subject: RE: ESX and NetApp best practice question Netapp didn't mean "OS swap" :) They aren't aware of what OS is inside of your vm's or if it has a swap. BTW, if the swap disappears under windows it will BSOD for sure. They were referring to the host swap, heh... jlc From: Andy Shook [mailto:[EMAIL PROTECTED] Sent: Monday, August 25, 2008 12:10 PM To: NT System Admin Issues Subject: ESX and NetApp best practice question List, Friend of mine is implementing ESX 3.5 on a filer and he is asking me if he should follow NetApp's advice on separating out the swap files on a different LUN to better "manage" snapshots. Now, I'm not a NetApp dude but I don't by this for the following reasons: 1. Another layer of complexity 2. Properly sized VMs (RAM) shouldn't be tapping the page file that much 3. Something happens to that swap LUN and performance tanks and/or OS blue screens 4. Recovery issues. (This maybe a stretch) I say keep the swap\temp directory on the same volume unless some non-standard requirements come into play Any of you NetApp\ESX admins have any feedback? Shook ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ -------------------------------------------------------------------- mail2web.com - Microsoft® Exchange solutions from a leading provider - http://link.mail2web.com/Business/Exchange ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
