I wonder if one could somehow use the AMVAULT command to do this? It serves to make a COPY of a dump tape (as I understand it).
At the very least, you could have a cron job copy the tape back *off* of the tape, onto a spare corner of the holding disk that you had labeled as “virtual disk” tape storage. Or, no wait ….. do that on-disk copy first. Have the holding disk data saved to another portion of the large disk area that is a “virtual disk tape storage” as your nightly backup tape. But since you really want a physical tape (I gather you do? I do.) then use AMVAULT to copy the virtual disk off to the real tape that you want. Every night. This would leave you with a copy of it on virtual disk. Which could be set up to have a very short recycle period, if you like? (Assuming you don’t have *that* much space to spare.) Maybe play with this idea a bit? Deb Baddorf Fermilab ( sorry for capitalizing words like AMVAULT — my mac keeps trying to change the spelling of words that I write) On Jan 26, 2015, at 12:09 PM, Jason L Tibbitts III <[email protected]> wrote: >>>>>> "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<
