Chuck Ciesinski wrote:

> 1.  From your most current 'Fullbackup', hopefully created with the
> 'DIRECTORY' option,

oh yes!  please make sure that you use the directory option (on some tape
(acknowledging different backup strategies))

>      restore your directories.  This will enable the system to
> re-establish connectivity to
>      application volume sets.

...otherwise you've got a bloody mess trying to figure out what the
permissions and capabilities used to be.

> 2.  RESTORE any accounts not on application volume sets.  Generally, our
> recommmendation is to keep third party tools and accounts on the system
> volume set.

<hrump> i'll polite disagree on this point -- but it has a lot to do with
the size of your system.  taking a page from the 'ken sletten school of
system management' (hi, ken :-) i like his approach (and have it on my
systems) to put as much of your 3rd party stuff onto it's own volume as
possible.  some 3rd-party sw isn't happy unless its on the system volume --
not mch you can do about that.  for the other stuff, isolate from the system
volume and your data volume(s).

> One of the first I restore      is VESOFT right after SYS and TELESUP.
> With their tools, putting your system back together again is a little
> easier.

or to expand this thought -- restore what you need to make life easier.  for
me, it would be our 'lib' account.  if you run qedit from the robelle
account -- by all means, restore it so you don't have to use editor :-) (for
example).

> Before the need occurs, make sure you have your critical files on your
> SLT, like EDITOR.PUB.SYS, FCOPY, and STOREXL, STORXL51 and STORXL52 if you
> use TurboSTORE with parallel writing.

absolutely!  there was a good discussion about what to put on your slt
awhile back and still on raven (someone want to go find it?).  you want your
slt to have enough on it to give you a usable system in the event of having
to do a system recovery.  making sure editor is on the slt is an excellent
beginning....

the key to do a successful (see?  i know what i'm doing :-) system recovery
is having 'stuff' in place ahead of time.  i've got a couple of little jobs
that get run on my bigger boxes each week to help recover the system.  i run
buldjob (it's ugly...but...), i make sure sysstart resides on ldev 1 (and
has the correct security), i dump the system configuration to a file.  none
of it's hard to do...it's easy to set up...and i think every system manager
should do it.     - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

Come, my friends, 'Tis not too late to seek a newer world.
Tho' much is taken, much abides; and tho'
We are not now that strength which in old days
Moved earth and heaven, that which we are, we are.
"Ulysses", A. Tennyson

>>>MY opinions, not Longs Drug Stores'<<<

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