On Tue, 10 May 2005, Brian Cuttler wrote:
> It sounds like a good feature - if you have enough holding area
> you could even hold files for a configurable number of days.
> 
> You'll need a way to differentiate held files from ones that didn't
> properly flush though, perhaps moving to a subdirectory of the
> holding area, YYYYMMDD-HELD or modifying the file name somehow.

Would it be possible to replace taper by a wrapper that uses `cp -l' to create
a hardlinked copy of the backup data first?

> On Tue, May 10, 2005 at 07:06:48PM +0200, Andreas Sundstrom wrote:
> > SND wrote:
> > > i want the backed up files from a nightly amdump-run to remain on the
> > > holding disk (after they were successfully written to tape!) at least for
> > > one day. So it would be possible to do faster and more comfortable 
> > > restores
> > > the next day.
> > > 
> > > Is there an option to acomplish that? And if there is one, is it possible 
> > > to
> > > force amanda to remove that data after a defined period of time?
> > > 
> > > 
> > > Many thanks in advance and best regards,
> > 
> > Not that I know the answer, but when I think about it I totally agree 
> > with this being a great function. I would immediatly configure my system 
> > to leave the last nights backups on disk until the next job starts, then 
> > it could purge yesterdays data if it was successfully written to tape.

Gr{oetje,eeting}s,

                                                Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert AT linux-m68k 
DOT org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                                            -- Linus Torvalds