One item that has not been mentioned in this 'sanity check' are 'spool files'.
I ran into it 2 weeks ago and it is still fresh in my mind.

Spool files during a 'reload' need to be restored with the 'nokeep' option.
This is because the 'spool file id' counter gets reset and since 'restored'
spool files get assigned a NEW 'SFID' the possibility of SFID conflicts exists
(30 spool files failed to reload in my case).

Perhaps HP should consider a 'RELOAD' keyword on their restores that 'enforces'
all these 'requirements'?.

Regards
Paul H. Christidis

____________________Reply Separator____________________
Subject:    Re: was Reload sanity check/ now Reload security check
Author: [log in to unmask]
Date:       10/27/99 11:29 AM

I agree with the concept of breaking up the restores into multiple parts.
The only modification I would make is that on the backup you store all the
system directories.  Then when you do the restore you would restore the
directory:

restore @[log in to unmask];SHOW;OLDDATE;KEEP;DIRECTORY

The restore of the system directories recovers the system accounting
structure and the account, group and user capabilities, passwords and access
rights.  The CREATE option will rebuild the accounting structure but will
not recover capabilities or passwords.  All created accounts, groups and
users are created with default capabilities.

If  after all files have been restored, if there are files that don't
restore because the creator doesn't exist then another way of addressing
this issue is to perform an additional restore:

restore @[log in to unmask]@;SHOW;OLDDATE;KEEP;CREATOR=manager

This would restore only those files that originally did not come back due to
the creator problem and would alter the files creator to "manager" or to any
user you specify.


<snip>