I’m not concerned with making them faster, I just don’t see any reason for snapping a TB or so of swap files offsite.

 

 

“1) The swap wants reasonably fast disk”

 

With 500 vms I’d hope you have a decent amount of spindles to play with (it is certainly justified), if the swap needs to be really fast why not carve a dedicated aggregate for them and FC attach them.  I don’t see how putting the swap luns in a different volume on the same aggregate will make the swap any faster, other than removing ASIS from the equation.

 

- Hadrian

 

 

We are in the preliminary stages of moving our 500 VM system to NFS (from fibre). The goal is to SnapVault everything off site, and I’d like to use A-SIS on our production volumes if at all possible (our VMs are almost identical and 95% reads so this should give us a great level of compression). My question to you is this:

 

Should I put the swap file on a different VMDK and put that in a different volume? The reasoning behind this is that 1) The swap wants reasonably fast disk and 2) I think that the swap file will not “play nicely” with A-SIS, at least not as nicely as normal data and 3) There is no need to actually waste bandwidth snapping the swap file offsite since it’s not needed to recover the machines (as long as in a DR standpoint we create the drive that contained the swap windows will create it at boot).

 

Thoughts or experiences welcome.

 

 

This message (including any attachments) contains confidential
and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on
the contents of this information is strictly prohibited and may
constitute a violation of law. If you are not the intended
recipient, please notify the sender immediately by responding to
this e-mail, and delete the message from your system. If you
have any questions about this e-mail please notify the sender
immediately.