I just want to add some more info here:

Actually it is not the CFI info that slows down the process. Of course, it will 
need some time to read some million file entries. However, this just takes 
minutes. I don't remember the UNIX recover GUI but on Windows you can actually 
see the filenames rushing through (at the bottom of the window) very fast 
during this process. The next step i have been told is an internal 'sorting' 
process - and this is the troublemaker. As you have seen, it can take hours 
before the program releases the GUI and hands control to the user again. And 
this has been fact for years.

As the save set recover process does not need the time to read and 'sort' the 
CFI info, it is not necessarily faster but it can act right away. As George 
said, you need to use the proper save set recover sequence and you should 
cleanup unnecessary files later.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER