>Hi Ed,
>
>Thanks for the information. I have another question.
>
>Right now, we have 3 physical drives in our RAS server.
>
>Disk 1
>C: 300MB
>D: 4GB
>
>Disk 2
>D: 2GB
>
>Disk 3
>D: 4GB
>
>We have recently added Disk 2 and Disk 3. Before, the swap file existed for each logical drive, both C: and D:. Now however, the ideal location for the swap file would be on Disk 3, but how do we know that's where the file will exist. Is there a way to force the swap file to that physical disk while it is part of that volume set?
>

Nope. I'd advise strongly against putting a swap file on a volume set, because you have no control over which part of the disk is used, so when the swap file expands or contracts, you are virtually guarenteed to fragment things in the swap file, and paging may now involve sections of several drives seen and addressed as a signle volume. I avoid volume sets like the plague IAC; there's no advantage to a volume set (at least IMO when compared to a stripe set without parity; neither provides and fault tolerance, but a stripe set can offer significant boosts in disk performance.)

Putting a swap file on a stripe set, OTOH, offers significant performance advantages. I'd take a look at http://www.ntfaq.com to get a better idea of what's going on AFA NT swap files.

I'd recommend getting someone who knows about NT to set this up; it looks like things were not thought out well with the system configuration.

>I'll take any suggestions...

If you insist on using a volume set, then take the last drive remove it from the volume set, partition it into two logical partitions, one a part of the volume set, and the other for use as swap file space, and then add the first partition back to the volume set. Allocate swap file space on the partition that isn't part of the volume set. I'd really recommend rethinking how the disk storage is managed on this system; if it's a server, it's a disaster waiting for a chance to happen.