HP3000-L Archives

November 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Craig M. Lalley" <[log in to unmask]>
Reply To:
Craig M. Lalley
Date:
Sun, 18 Nov 2001 14:35:30 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (76 lines)
I am sure you already caught this, but just in case.

When you run BULDACCT, make sure you use the onvs option to point to the
NEW volume set you intend to install on.

-Craig

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Thomas M. Root
Sent: Sunday, November 18, 2001 1:57 PM
To: [log in to unmask]
Subject: [HP3000-L] Help with install on new disk drives

I'm in the process of migrating our 3000s from local disk drives to an
EMC
symmetrix.  I won't change the production system until after the first
of
the year, but I plan to change the test system this week.  I haven't
done a
migration like this since I used a Series II in 1979.  The concept looks
the
same, but I'd like some advice on the 'new' details.

The test system currently has a mix of 1.3G, 2G, and 4G drives (20
total)
all in a single system volume set.  I,m going to replace all the current
drives with 10 logical 4G drives; 2 in the system volume set and 8 in a
user
volume set.  I've run BULDACCT and done a full system backup and verify.

My plan is to make a CSLT with a store of everything I want to place on
the
new system volumes.  Then, I'll shut the system down, remove the current
drives and controllers, connect the new controller and drives, and do an
INSTALL from my CSLT.  When the system comes up, I'll stream the
BULDJOBs,
restore the files from the CSLT to my system volume, build the remaining
accounts on my user volume, and restore the user files from my backup.

1. Am I on the right track here?

2. Can I configure the new drives during the INSTALL or should I do that
when I make the CSLT?

3. Am I correct that if things don't work, I can put my original
controllers
and drives back, boot from the appropriate path, and have everything
back as
it was before?  (ie 'Live to try another another day')

4. Can I initialize and label 'new' disks as part of the INSTALL or do I
need to use a running system to create scratch disks?

5. Have I left out anything?

In a seperate, but related issue, my production system has 7 2G drives
in a
HAAS box that is connected to a single ended SCSI controller.  DSTAT All
shows all the drives having SCRATCH status.  Can I power down the box
and
unplug the cable from the controller without shutting down the system?

Thanks,

Thomas M. Root
Desert Schools Federal Credit Union
[log in to unmask] <home>
[log in to unmask] <work>

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

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

ATOM RSS1 RSS2