HP3000-L Archives

August 1999, Week 1

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:
"Michael P. Smith" <[log in to unmask]>
Reply To:
Michael P. Smith
Date:
Wed, 4 Aug 1999 15:11:00 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (67 lines)
Donna Garverick wrote in message ...
>hi all~
>
>i have a system that has a collection of disc drives --
>wholly contained in two jamaica enclosures -- that i want to
>move to another system *with* the data and directory
>structure intact and have the new system recognize the
>everything.  (that's is no restore from tape....)  i talked
>to my ase about this.  he said it was doable and gave me the
>following....
>
>1.    Back up all data on volsets to be moved
>2.    Use BULDACCT to create accounting structure as you
>would want it in case of a need to manually rebuild volume
>sets
>3.    Shutdown the donor system
>4.    Configure the disc mechs on the target system
>5.    Add any accounts as needed on target system (this may
>be the tricky part).  You will not be able to use ;ONVS yet,
>as the sets are not there.
>6.    Shut down the target system
>7.    Move cabling for the drives to the target system
>8.    START NORECOVERY on target system
>9.    Check for disk drives
>
>i thought i'd better pass this by y'all before i tried
>anything.  it would seem to me that all is not quite
>right....  why use buldacct (step 2) if you're not going to
>use it?  what about step 5?  assuming this were to actually
>work...i have to live with the private volume names,
>right?               - d
>
>--
>Donna Garverick     Sr. System Programmer
>925-210-6631        [log in to unmask]
>
>>>>MY opinions, not Longs Drug Stores'<<<
>

Donna,

   I probably would use the BULDACCT jobs created in step 2 to make the
accounting structure on the new system.  It is easier (in my opinion of
course) to run these jobs rather than trying to remember what
accounts/groups/users are on the private volume set (oops...non-system
domain volume sets that is:) ) and not to mention what UDCs the users might
have set.

  As for the private volume names....yes you will have to live with them.
Back in the 4.0 days I tried renaming a volume set by hand (via :DEBUG's
MSEC command).  It never quite worked.  Once or twice it came up okay, but a
couple of other times the drives were in accessable.  When I asked HP about
it they informed me that no one has every requested the ability to rename a
volume set....officially.  So I dropped it.

   Hope this helps.

 ---------------------------------------------------------------
| Michael P. Smith                                              |
| Sr. Systems Programmer                                        |
| The Hertz Corporation    [log in to unmask] (work)          |
| Oklahoma City, OK                                             |
 ---------------------------------------------------------------
The thoughts, views and expressions contained in this message are those
of Michael P. Smith, and do not necessarily reflect those of the Hertz
Corporation.  To reply via email, remove the .xx from email address.

ATOM RSS1 RSS2