I am well aware of the best practice of two restore to effect a reload.

The first restore simply makes the entire system directory as it was at
backup time with all groups accounts and paths.

The second restore puts the data back.  And it should also restore all HFS
files, whether /-based or group.account based.

My concern is that I cannot seem to be able to NOT restore HFS files using
the @[log in to unmask]@ construct.  In other words, what occurred to start this thread
should not have happened.

Denys

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On Behalf Of
Goetz Neumann
Sent: Friday, February 14, 2003 3:02 AM
To: [log in to unmask]
Subject: Re: reload and posix

Denys Beauchemin wrote:

> I also hate leaving such a mystery unsolved.  This should make sense
> somehow.  But I am afraid that with the data at hand, it will have to
remain
> so.

>>:RESTORE *T;@[log in to unmask]@;/QDX/@/@;DIRECTORY;CREATE;OLDDATE;KEEP

Ever since I joined HP Support in 1990 here in Germany we
always advocated to customers in a reload situation to
do 2 RESTOREs.

1) RESTORE *t;;DIRECTORY
2) RESTORE *t;@[log in to unmask]@;keep;olddate  (maybe add ;create)

I cannot exactly tell why, I just know for certain that it
avoids some oddities.
I searched our databases and found a reason for it, when you
restore from parallel devices (which was apparently not done
in this case).
It is also possible that when you use ;CREATE _and_ ;DIRECTORY
it might only create directories for files on the tape that do
not belong to the directories that were saved onto tape.


Goetz.

* 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 *