I have recently added a set of disks (file systems) to my back-up set and that ended up with a failure due to "data timeout". I didn't even know there was a dtimeout value to be specified in amanda.c
I may be totally wrong here, but I don't think it is tracking "idle" time. I believe it is total time to dump. This would take care of "stuck" or "runaway" dump scenarios. -- Jon H. LaBadie jon AT jg
The documentation says: dtimeout int Default: 1800 seconds. Amount of idle time per disk on a given client that a dumper running from within amdump will wait before it fails with a data timeout error
Author: Matt Hyclak <hyclak AT math.ohiou DOT edu>
Date: Tue, 23 Aug 2005 11:24:20 -0400
On Tue, Aug 23, 2005 at 05:04:02PM +0200, Erik P. Olsen enlightened us: Yes, and that "per disk" is important. If you have a machine with 3 Disklist Entries (DLEs), it will wait 5400 seconds (90 minu
Glad I said I may be totally wrong :( Thanks, -- Jon H. LaBadie jon AT jgcomp DOT com JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Author: Graeme Humphries <graeme.humphries AT vcom DOT com>
Date: Tue, 23 Aug 2005 09:36:26 -0600
Jon LaBadie wrote: The documentation says: dtimeout int Default: 1800 seconds. Amount of idle time per disk on a given client that a dumper running from within amdump will wait before it fails with a
Author: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Tue, 23 Aug 2005 17:51:25 +0200
I have recently added a set of disks (file systems) to my back-up set and that ended up with a failure due to "data timeout". I didn't even know there was a dtimeout value to be specified in amanda.
I read it the way that each disk gets 1800 seconds idle (wait?) time before a time out. That is if disk 1 uses 1 second of that time the rest of 1799 seconds is "lost" and will not be added to the id