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.