I tend to only use the internal drives on any system for dump-to-disk and
everything else either goes to an XP array or SAN.

Keeping a bootable image of MPE on one of the internal drives is an
excellent point, it saved me once at 2 AM when we lose total connectivity to
the XP array the system was attached to and we had some serious trouble
shooting to do

Jim

"Goetz Neumann" <[log in to unmask]> wrote in message
news:421afb0d$1@usenet01.boi.hp.com...
> donna garverick wrote:
>
> > --- Jacqueline Savinon <[log in to unmask]> wrote:
> >
> >
> >>What internal storage options are available for an N-Class and a 997
> >>(both MPE)? Can the N-class take advantage of Fibre with internal
> >>drives and as a direct connect to the network?  TIA
> >
> >
> > i think the internal drive question has been answered well....
> >
> > my advice is -- if you are connecting an n-class server to a va or xp
> > array, then put *all* your drives on the array.  the risk of those one
> > or two internal drives failing far outweigh any perceived risk of
> > trying to boot from an external drive.  you'll sleep much better
> > knowing that your entire system volume is protected on the array.
>
> while I agree on the protection aspect, I would suggest to leave
> a bootable MPE Image on an internal disk.  This can be very handy
> e.g. to run offline diagnostics from it,  and if you'd had SAN
> trouble, you could run ODE Mapper to find them FC disks 'out there'.
>
> Goetz.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *