Jim,
In response to each question:
1) If best means cheapest/easiest, then a Model 10 or Model 20 array would
be more appropriate. However, if you add "support life" to the definition,
then an AutoRAID is a better choice. Both serve as bootable devices and
provide protection for the MPEXL_SYSTEM_VOLUME_SET (or long name, as you
refer to it).
2) The AutoRAID 12H requires MPE/iX 6.0 or greater. It will work with 5.5,
but it is not recommended for reasons of configuration complexity. The ARM
utilities are easy to use and the AutoRAID manuals provide enough
information and direction to configure it. As long as you are comfortable
with attaching the fast-wide cable to the controller. NOTE: HP only supports
one controller for connectivity to the HP 3000.
3) The AutoRAID will provide "data redundancy" for all volume sets. One of
the benefits of AutoRAID on MPE/iX is the ability it provides to protect the
System Volume Set (since you can't protect the system volume set with
MirrorDisk/iX).
I prefer not to mix System Volume Set and User Volume Set data on the same
I/O channel. In your case, with the limited disk capacity, you would almost
certainly have ALL of your data on the AutoRAID. This means all I/O through
one (fast-wide)channel. Not knowing the nature of your app, this may or may
not, be reason for concern. I have been told by certain HP folks that the
disks will be the bottleneck before the channel becomes an issue, even on a
fully loaded AutoRAID...
Regards,
> _________________________________________
>
> Rocky J. Costantino
> Vice President
>
> Computer Design & Integration, LLC
> 696 Route 46 West
> Teterboro, NJ 07608
>
> * e-mail [log in to unmask]
> * Web http://www.cdillc.com
> * Phone (201) 931-1420 x224
> * Fax (201) 931-0101
>
>
-----Original Message-----
From: Jim Phillips [mailto:[log in to unmask]]
Sent: Friday, May 12, 2000 2:04 PM
Subject: 12H Array
I've read the documents on HP's web site about the 12H array and it looks
like something we may be able to use; that is, I'm looking for some kind of
disk array to alleviate the pain, frustration, and horror of disk failures
and this looks like it.
But, as usual, I have some questions:
1) Is this the "best" way to achieve data redundancy? (Best in this
instance means the cheapest, easiest way) We only have 12 GB of disk space
now (about 75% utilized) split over 4 physical drives, but will need to add
another 4GB drive soon (I have a 3312 HASS enclosure that only has two
drives in it and can hold eight).
2) If we purchase the 12H (probably from a third-party vendor) can I
install it? (That is, can someone with a modicum of mechanical ability who
is not afraid of opening up an HPe3K - I've installed memory chips before -
install it)
3) We only have the "long name" volume set right now. However, I would
probably go with a user volume for our ERP application with a 12H. I can
use the 12H to provide data redundancy for both the "long name" and user
volumes, right?
Any other comments or questions or things to watch out for may or may not be
appreciated, depending on how rude they are....
Thanks, as always,
Jim Phillips Manager of Information Systems
E-Mail: [log in to unmask] Therm-O-Link, Inc.
Phone: (330) 527-2124 P. O. Box 285
Fax: (330) 527-2123 Garrettsville, Ohio 44231
|
