Adding the ";VOLSET=MPEXL_SYSTEM_VOLUME_SET "  does not select files only
for the system volume set, instead it says to try placing restored files to
the MPEXL_SYSTEM_VOLUME_SET.   This means you could potentially have
recently purged files from various accounts on other private volumes
restored back into the system volume set.

What I've found that works well --- is to do a restore of the directory
first:

restore *tape;;directory

Then do a REPORT x.@;onvs=mpexl_system_volume_set      (to a file if
necessary)

Then build an indirect file with the account names  --- using the POSIX
"/account/" format.

Also do a listfile and look for some of the POSIX directories that you
might have overlooked.... make sure you include these in the include file.

Finally restore with keep;olddate;create=creator...  all done in a batch
job.


The above process -- even with hand editting of the include file,  is much
faster than the blanket @[log in to unmask]@ restore with olddate;keep.   The reason is
that with the @[log in to unmask]@ option, MPEiX will pull the file off the tape, start
the restore process for it, then discovers that it already exists, generate
an error messages and then repeat the process for the next file.  It isn't
smart enough to know that the files on the other private volume groups were
okay and can be skipped.


A better process is actually build a job or script that creates the
indirect file (with correct accounts) for each volume set every night
before the backup is done.  Then if you loose a private volume, all you
need to do is restore the directory, that file and begin the rebuilding
process.

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