Solved

VMWARE on SAN and Windows paging file question

Posted on 2007-11-26
5
3,729 Views
Last Modified: 2013-11-14
I am about to build a Win2003 server on a VMWare ESX with SAN. It's an initial installation, which will - in the future - contain of 2 SANs connected by a slow (5Mbps) link for replication purposes (DR site). Also, the primary site will have 2 VMWare hosts connected to the same SAN for failover with VMotion, where the secondary only one host with it's own SAN. However, this latter is not an issue for the sake of this question. My primary concern is the performance and the amount of the data that will be replicated between the primary and secondary site SANs. I could go simple by creating one VM storage per O/S and install Win2003 together with it's swap file onto it. It's easy to manage. However my primary concern is that the paging file and it's frequent changes, would generate a lot of replication traffic, which would be completely unnecessary. I am not planning to do VMotion between the sites. How do I come about this problem? Shall I create a separate LUN on the SAN only for the purpose of the paging file and specifically tell Win2003 create a paging file on a different drive? I am a complete newbie when it goes about the SAN, we have contractors setting this up for us, and I would throw the problem on the forum to hear different approaches before I accept their solution.
0
Comment
Question by:groobo
  • 3
5 Comments
 
LVL 23

Expert Comment

by:Iamthecreator
ID: 20351373
Set the paging file size SYSTEM MANAGED and let Windows do the management.
 
0
 

Author Comment

by:groobo
ID: 20351777
That's not what I am asking; it's not a Windows question; more like VMW/SAN. If I keep the paging file on the volume (drive) with windows, and elect the replication of this volume, I am creating additional SAN replication traffic across sites, which is not necessary as I do not plan doing VMotion across the sites. That's why I am thinking about creating LUN specifically for the paging file for which the snapshots and replication between sites would be disabled.
However, I would still like to use the VMotion for 2 ESX hosts connected to the same SAN locally. Now the question is, will a separate LUN for the windows swap be somehow limiting to the local VMotion?
We have 3TB NetApp SAN here that 'understands' VMWare, as I have seen at initial configuration of the volume.
I hear different opinions, that's why I would like to ask the experts for best practice.
0
 

Author Comment

by:groobo
ID: 20352737
Clarification: In above, I am talking about LUNs, where I shall rather talk about volumes. Some system/data volumes will be mirrored, where swap file volumes won't.
0
 
LVL 21

Accepted Solution

by:
robocat earned 300 total points
ID: 20352808

NetApp recommends putting the host swap files on a different VM datastore (or LUN on the NetApp). As long as you keep this datastore on shared storage, you should be able to use VMotion.

You could consider replicating this LUN to your DR site also, but less frequent, because this will make recovery during a disaster a little more easy.

We ourselves don't separate the swaps from the host directories, but we don't over commit the VMWare RAM, so there's not much paging going on.
0
 

Author Comment

by:groobo
ID: 20353317
Found this on NetApp:

[…] Virtual machines should have their swap files, pagefiles, and user and system temp directories moved to separate virtual disks residing on separate datastores residing on NetApp volumes dedicated to this data type. In addition, the ESX servers create a VMware swap file for every running VM. These files should also be moved to a separate datastore residing on a separate NetApp volume. Figure 33 shows an example of this data layout. [...]
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Lets start to have a small explanation what is VAAI(vStorage API for Array Integration ) and what are the benefits using it. VAAI is an API framework in VMware that enable some Storage tasks. It first presented in ESXi 4.1, but only after 5.x sup…
How to update Firmware and Bios in Dell Equalogic PS6000 Arrays and Hard Disks firmware update.
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now