From: "Robert Comer" 

> First of all, the boot partition is on the mirrored set, doesn't that
> mean if one of the pair blows I can still boot because the other one
> still works?

Most likely, but you may need a special boot up disk -- it all depends on
what your controller reports to NT as to what would happen.

>Secondly, I  want the swap file on the solo disk, i.e. not
> the other partition of the mirrored set that has the OS partition.   So
> doesn't that mean that for your scenario to happen both disks in the
> mirrored pair would have to blow, PLUS the solo disk?

Nope, all that has to be down is the solo disk, if that's the only place
the swap is, no solo, no full boot. (NT actually trys to come up but you
can't log in.)

>We do have some
> extra disks lying around, I could ask the server guy to make one that
> looks just like the single one so if the single one blows we just pop it
> in...   ?

It'd be easier to keep a minimal swap file on the boot disk...  (I always
do now.)  I really don't think it would impact your performance enough to
even notice as long as it's minimal.

- Bob Comer



"Ellen K."  wrote in message
news:o1a93v4sf1i0gjktig085soisc5njgt6nb{at}4ax.com...
> First of all, the boot partition is on the mirrored set, doesn't that
> mean if one of the pair blows I can still boot because the other one
> still works?  Secondly, I  want the swap file on the solo disk, i.e. not
> the other partition of the mirrored set that has the OS partition.   So
> doesn't that mean that for your scenario to happen both disks in the
> mirrored pair would have to blow, PLUS the solo disk?   We do have some
> extra disks lying around, I could ask the server guy to make one that
> looks just like the single one so if the single one blows we just pop it
> in...   ?
>
> On Sun, 26 Jan 2003 20:57:50 -0500, "Robert Comer"
>  wrote in message :
>
> >There is one problem in not having a swap file on your system
partition --
> >should the partition your swap is on not be available fore some reason,
NT
> >wont boot. (so you can't get to any of the GUI tools to fix not having
your
> >swap file partition)
> >
> >- Bob Comer
> >
> >
> >"Geo."  wrote in message
news:3e34834a$1{at}w3.nls.net...
> >> I'd probably need it to crash 2 or 3 times before I resorted to trying
to
> >> make sense out of a dump file. I find the event (and other sources) log
> >much
> >> more useful.
> >>
> >> Geo.
> >>
> >> "Ellen K."  wrote in message
> >> news:cqe83vod9i9vekr3apj3c8r1aa3enrco8n{at}4ax.com...
> >> > IOW if it crashes once, put one back on C in case it
crashes again,
> >> > otherwise don't worry about it?
> >> >
> >> > On Sun, 26 Jan 2003 13:30:23 -0500, "Geo."
 wrote in
> >> > message :
> >> >
> >> > >"Ellen K."
 wrote in message
> >> > >news:efk63v4n9ve4pdtr61f3rbb8pgi6qad2h4{at}4ax.com...
> >> > >
> >> > >> For performance reasons I wanted the swap file
to be on the solo
> >drive.
> >> > >> I was able to create one there, no problem.  
However, according
to
> >> some
> >> > >> message boxes etc apparently I *HAVE* to have
one on C if I want
to
> >> > >> capture dumps in case of crashes.   Is there
any way I can make
the
> >one
> >> > >> on C *ONLY* be used for that purpose, and use
the one on the solo
> >drive
> >> > >> for normal swapping?
> >> > >
> >> > >Just ignore the requirement for dumps, nobody uses them anyway
unless
> >you
> >> > >have some serious problem that isn't going away and
in that case you
> >can
> >> > >always re-enable the feature and create a swap on
C:. It should not
be
> >a
> >> > >requirement of a production db because the production system
shouldn't
> >be
> >> > >crashing and dumping .
> >> > >
> >> > >Geo.
> >> > >
> >> >
> >>
> >>
> >
>

--- BBBS/NT v4.01 Flag-4