On Fri, Feb 22, 2008 at 12:48 PM, Gordon J. Mills III <[EMAIL PROTECTED]> wrote: > I have recently run into a problem with restoring. I want to restore a > folder on a DLE that is about 100G. The folder I want to restore is small > but apparently Amanda has to restore the entire DLE to get at the 1 folder. > It is restoring the large file to /tmp/Amanda/. Unfortunately, I do not have > enough room there to extract the entire DLE.
Are you using amrestore or amrecover? Amrecover will only actually write the files you have requested to disk, although your observation that it reads the entire dump from tape is correct. > My first question is: How can I have Amanda use a different path for this > task. I have an NFS mounted external drive that has much more room on it. If you're using amrecover, you should 'cd' into the directory into which you want to recover your files before starting amrecover. > 2nd question: Is there a way to setup Amanda so that it does not have to > retrieve the entire DLE file? Is it just removing compression from the DLE > def? Or chopping up the DLE to smaller chunks (this will be hard since most > of the data is in 1 place on that dle). Currently, that's the only solution -- smaller DLEs. > I would like for Amanda to behave in a similar way that I have had other > backup software behave. That is, if I just want a single file or folder, > then it scans the tape (in this case vtapes) and retrieves only what I want. > When I have successfully retrieved files with Amanda before it took a very > long time. Is there a way to set it up so that it will do this? Not yet, but that is a major aim of the Application API and transfer architecture, which are under active development. For a hint as to how complex this is, see http://wiki.zmanda.com/index.php/User:Dustin/Data_Handling_Model. There's no specific ETA on this development at the moment. Dustin -- Storage Software Engineer http://www.zmanda.com
