>>>>> "JM" == Jean-Louis Martineau <[email protected]> writes:
JM> The main problem is that if you leave the dump in the holding disk, JM> amanda will automatically re-flush (autoflush) them on the next run. JM> There is no way to store the information about dump that are already JM> flushed and dump that are not flushed. Well, I figured as a hack, they'd just get renamed in some way that the code would ignore when it comes to flushing things, and a cron job would nuke the oldest ones every few minutes if the disk is full. But of course that wouldn't integrate the held dumps with the regular restore process. JM> The amanda development branch have that capabilities. Implementing JM> this feature will be a lot easier. Cool. It's not as if I'm in a huge hurry. I just thought it might be nice to use the holding disk for more than just a very temporary staging area. - J<
