Ed,
I think you
misunderstood.
“The
next thing you should do is determine where your pagefile is located on
physical drives. Ideally it should be local (not on a SAN drive) and should not
exist on the same physical drive as the operating system. An exception to this
could be if you have raid on the local disk.”
What I meant to
convey is that if you have 2 physical disks and one is C: and one is D:, and
the OS is installed on C:, you’d want your pagefile on D:
The reference
to an array was meant to reference the fact that, as an example, if you have 5
disk in a RAID 5 array, and C: and D: were both on that array, it wouldn’t
matter which logical volume the pagefile resided on. The same would hold true
for a mirrored pair.
That is what I
meant by “An exception…”
-Kent
From: Ed Wilts
[mailto:ewilts AT ewilts DOT org]
Sent: Friday, July 17, 2009 10:51 AM
To: Eagle, Kent
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Which is Best for My NetBackup Master - 32
On Fri, Jul 17, 2009 at 9:04 AM, Eagle, Kent <KEagle AT wilmingtontrust DOT com>
wrote:
Avoid putting a page file on a fault-tolerant drive, such as
a mirrored
volume or a RAID-5 volume. Page files do not need fault-tolerance, and
some fault-tolerant systems suffer from slow data writes because they
write data to multiple locations.
This is crazy! If you have a hardware failure on a disk that hosts the
pagefile, you *will* crash. You obviously want a decent raid controller,
but there's no way I'd avoid a hardware-mirrored volume just for performance.
If your access to the page file is that high that you are saturating a mirrored
disk, then you've got major memory constraint issues to deal with. Fault
tolerance is the least of your problems.
Disks do exactly 3 things:
1. They read
2. They write
3. They fail
.../Ed
Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewilts AT ewilts DOT org
