This is exactly what we see.

We make great efforts to keep our volumes small (our largest is about 150GB) 
and we backup by volume (one per class).  This is for many reasons -- the 
ability to restore the whole volume in a management - directed window, the 3.2 
issue with resources and the HIST parameter (if you run 3.2 with NDMP, you 
should understand this -- use of the HIST parameter could prevent single 
file/dir restores), keeping the image as small as possible for restores, etc.

Also, when we went to 3.2 and started looking into the java gui, it became 
apparent that a keyword would help.  When I select a restore from the filer 
toaster vol0, it appears that the java gui would look at all the images for 
toaster, even though I am backing up by volume and it only has to look at vol0 
images.  In the Motif gui, you could select the image to look at.  So, so help 
with restores usng the java gui, I put a keyword on all the classes (filer.vol) 
and can enter that keyword on the restores.

Kelly


--

Kelly Wyatt, Kelly.Wyatt AT SAS DOT com
Systems Programmer
Integrated Solutions Consulting
SAS Institute Inc. / SAS Campus Drive / Cary, NC  27513
http://www.sas.com