I did something similar to this in the early 90's when working for a
pharmaceutical benefits manager. We were 24x7 and the downtime cost was
real. If we did not process a prescription, we did not get paid. The task
that I had to accomplish was to dismantle a 40 disk system volume set into
multiple private volume sets on new disk drives. Store/restore was out of
the question.
You can eliminate the tape intermediary *if* you can attach the array to
your system, have access to the original drives, have a fast buffer mode
disk file copier such as MPEX from VESOFT<unintentional plug>, and a
wildcard file rename <MPEX again>.
You didn't mention if the original disks all belong to the system volume
set. If they do, you will have to create a system volume set on the array
and install MPE on this volume setto be able to boot from the array. Also,
now is probably a good time to migrate your production accounts off the
system volume set.
Also, during the time you migrate a group, you will have to deny access to
all users, as you will be copying the files and need to have exclusive
access.
1. Backup system
2. Create a new volume set for on the array
3. Build the accounts that you wish on the new volume set
4. Create a temp group for each account and *home the group to the new
volume set*
5. Copy all of the files from a group to be migrated to the temp group
6. Verify that all files have been copied
7. Purge all of the files on the original group
8. If original group was on a private volume set, purge group from that
volume set. Build group on new volume set and home group to new volume
set.
9. Rename files from temp group to original group.
Repeat 5-9 as many times as needed.
When you are all done, if you need to rebuild the system volume set,
install the operating system and restore all file with 'oldkeep' option.
There shouldn't be much on this volume set.

Most of the functions can be accomplished thru script files using wilcarded
commands(ie: %copy @.db.prod,@.temp.prod <MPEX again>)

Since this is a gradual approach, you can choose when you will incur
downtime and how much by your choice of group(s). Depending upon the
applications, it may be possible to limit downtime to specific users, as
their account is migrated. If you need to rebuild the system volume set,
this will be downtime for the entire system.

Hope this provides another option for you


rep
4. Copy all of the files in a grothe files ateh fileson egroupthe groups
that you are migrating. iogosusersThe advantage re will be some down time,
but you can decide timeisLast gotcha

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