Okay, I just answered my own question, and unfortunately, it's the ugly answer. DB2 gets very upset if you do a RESTORE DB ... CONTINUE and all the files are not there. When it runs out of data, it does not politely ask that you point it to the location of the next file, it simply says: SQL2538N Unexpected End of File of Backup Image reached on media "<backup filename>" There is no known way to resume the restore once this error occurs. Therefore, it appears that there must be enough space for all the destination tablespaces and all of the backup files at the same time, but those backup files can be compressed and read through a named pipe that uncompresses them on the fly (suggested by Dimitry). Because NFS shares are a very hot political topic in my shop, I did not try the option of mounting a remote share that contained all the files, but one would think that approach should work (albeit slowly). Thanks, Fred - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
