On Wed, 13 Jul 2005 [EMAIL PROTECTED] wrote:
> You could use a script that 'replaces' tar on the client and that checks
> to see if a job is still running, if there is, it waits with the tar
> command.
>
> I don't have the document describing the procedure with me right now, but
> I use this kind of scripts to shut down databases and/or other services on
> clients before I send the data.
This may work fine for `short' delays, but not for jobs that may take more than
a day. Then Amanda will time out.
Alternatively, make the client not accept amanda connections when it's busy, so
it looks like the client is powered down. As long as it's available at least
once during the dumpcycle, amanda will be happy to back it up.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
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
