RE: RE exclusions
Thanks fo your reply. My understanding (as far as that goes) has always been that amanda can only do full and incremental backups? I've been doing full backups because until now we've had the capacity to do that. If I switch to the way amanda should really work, then does that not mean that I'll get full and incremental backups, which will make the restore process more cumbersome in terms of the number of tapes needed for a restore? I'm still using amanda 2.4.4. Will appreciate your advice on this. From: Cyrille Bollu [mailto:[EMAIL PROTECTED] Sent: 10 October 2007 16:57 To: Johan Booysen Cc: amanda-users@amanda.org; [EMAIL PROTECTED] Subject: RE exclusions At first sight it looks very easy: You are currently only doing full-daily backups. So, switch to regular incremental/differential backups and you'll be fine (No need to ask people doing tar files...) Also, Amanda has all the features you need to keep track of where your files have been backuped. (eg: index yes in amanda.conf, amrecover, amtoc,...) What I want to do now is continue doing full backups every night, but exclude any data that will have been backed up to the monthly archive tape. IMHO, you are describing a differential backup scheme here. Cyrille
Re: RE exclusions
On 2007-10-11 10:35, Johan Booysen wrote: Thanks fo your reply. My understanding (as far as that goes) has always been that amanda can only do full and incremental backups? ?? ...only... ?? What other kind of backup are you hinting at? If you mean a http://www.backup4all.com/differential-backup.php;, then that's just an incremental level 1, which you can configure by setting e.g. bumppercent 100, or by setting bumpdays 9 (the latter one assumes you do run at least one other full backup within the next 273 years :-) ). I've been doing full backups because until now we've had the capacity to do that. If I switch to the way amanda should really work, then does that not mean that I'll get full and incremental backups, which will make the restore process more cumbersome in terms of the number of tapes needed for a restore? Yes, but not so complicated that a restore becomes an gigantic task. Moreover, then chance to need to restore a recently modified file is much larger than files that are never changed. And in that case restore from an incremental is much faster. How else would you like to solve the problem of too much data to fit on a tape? (besides removing the dead files.) I'm still using amanda 2.4.4. Will appreciate your advice on this. *From:* Cyrille Bollu [mailto:[EMAIL PROTECTED] *Sent:* 10 October 2007 16:57 *To:* Johan Booysen *Cc:* amanda-users@amanda.org; [EMAIL PROTECTED] *Subject:* RE exclusions At first sight it looks very easy: You are currently only doing full-daily backups. So, switch to regular incremental/differential backups and you'll be fine (No need to ask people doing tar files...) Also, Amanda has all the features you need to keep track of where your files have been backuped. (eg: index yes in amanda.conf, amrecover, amtoc,...) What I want to do now is continue doing full backups every night, but exclude any data that will have been backed up to the monthly archive tape. IMHO, you are describing a differential backup scheme here. Cyrille -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: RE exclusions
On 2007-10-11 12:03, Johan Booysen wrote: When I say differential I mean a backup that contains everything since the last full backup. Incremental for me means a backup that contains the changed files since the last backup, whether the last one was a full backup or not. If your incremental level 1 backup is actually the same as my differential backup, then I've completely misunderstood that whole issue until now. Level 0 == full backup Level 1 == all changed since the last level 0 == differential backup level 2 == all changed since last level 1 (you are trying to avoid the levels = 2, or did I miss something?) :0| Ok, so say I want to do 1 full backup each week (Monday - Friday) and differentials (everything changed since the last full backup) in between, what would you suggest for these in amanda.conf? bumpsize bumpdays Bumpmult bumpdays 9 is enough. Now Amanda waits about 273 years before considering a level 2 incremental backup. Or does it not quite work that way? I don't really understand what bumpdays, bumppercent and bumpmult do and/or how they do it. My apologies but I must be dim or something - tried to read up before sending this reply this but still lost (http://www.amanda.org/docs/amanda.conf.5.html). A coffee helps, and reading it three times again... Maybe you miss one point: Amanda first runs an estimate for different levels of backup. When a level 0 backup is not due, Aanda runs an estimate for level N (the level that was run the last time), and, if bumpdays have passed since the last bump in levels, she also runs an estimate for level N+1. When the estimates are done, Amanda picks a good level. Settings bumpdays 9 accomplished what you need, I believe. (It is better than bumppercent 100, which would maybe run an estimate for level N+1, which will later be decided as not to be good -- too much waste of time + machine load). Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Bijnens Sent: 11 October 2007 10:07 To: Amanda List Subject: Re: RE exclusions On 2007-10-11 10:35, Johan Booysen wrote: Thanks fo your reply. My understanding (as far as that goes) has always been that amanda can only do full and incremental backups? ?? ...only... ?? What other kind of backup are you hinting at? If you mean a http://www.backup4all.com/differential-backup.php;, then that's just an incremental level 1, which you can configure by setting e.g. bumppercent 100, or by setting bumpdays 9 (the latter one assumes you do run at least one other full backup within the next 273 years :-) ). I've been doing full backups because until now we've had the capacity to do that. If I switch to the way amanda should really work, then does that not mean that I'll get full and incremental backups, which will make the restore process more cumbersome in terms of the number of tapes needed for a restore? Yes, but not so complicated that a restore becomes an gigantic task. Moreover, then chance to need to restore a recently modified file is much larger than files that are never changed. And in that case restore from an incremental is much faster. How else would you like to solve the problem of too much data to fit on a tape? (besides removing the dead files.) I'm still using amanda 2.4.4. Will appreciate your advice on this. -- -- *From:* Cyrille Bollu [mailto:[EMAIL PROTECTED] *Sent:* 10 October 2007 16:57 *To:* Johan Booysen *Cc:* amanda-users@amanda.org; [EMAIL PROTECTED] *Subject:* RE exclusions At first sight it looks very easy: You are currently only doing full-daily backups. So, switch to regular incremental/differential backups and you'll be fine (No need to ask people doing tar files...) Also, Amanda has all the features you need to keep track of where your files have been backuped. (eg: index yes in amanda.conf, amrecover, amtoc,...) What I want to do now is continue doing full backups every night, but exclude any data that will have been backed up to the monthly archive tape. IMHO, you are describing a differential backup scheme here. Cyrille -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out *
RE: RE exclusions
Or maybe too many coffees..?! :) Ok - now I understand you loud and clear! Thanks very much! I'll do more reading because with my new understanding of Level 1 == all changed since the last level 0 things will make much more sense. Much appreciated! Thanks. Johan -Original Message- From: Paul Bijnens [mailto:[EMAIL PROTECTED] Sent: 11 October 2007 11:34 To: Johan Booysen Cc: amanda List Subject: Re: RE exclusions On 2007-10-11 12:03, Johan Booysen wrote: When I say differential I mean a backup that contains everything since the last full backup. Incremental for me means a backup that contains the changed files since the last backup, whether the last one was a full backup or not. If your incremental level 1 backup is actually the same as my differential backup, then I've completely misunderstood that whole issue until now. Level 0 == full backup Level 1 == all changed since the last level 0 == differential backup level 2 == all changed since last level 1 (you are trying to avoid the levels = 2, or did I miss something?) :0| Ok, so say I want to do 1 full backup each week (Monday - Friday) and differentials (everything changed since the last full backup) in between, what would you suggest for these in amanda.conf? bumpsize bumpdays Bumpmult bumpdays 9 is enough. Now Amanda waits about 273 years before considering a level 2 incremental backup. Or does it not quite work that way? I don't really understand what bumpdays, bumppercent and bumpmult do and/or how they do it. My apologies but I must be dim or something - tried to read up before sending this reply this but still lost (http://www.amanda.org/docs/amanda.conf.5.html). A coffee helps, and reading it three times again... Maybe you miss one point: Amanda first runs an estimate for different levels of backup. When a level 0 backup is not due, Aanda runs an estimate for level N (the level that was run the last time), and, if bumpdays have passed since the last bump in levels, she also runs an estimate for level N+1. When the estimates are done, Amanda picks a good level. Settings bumpdays 9 accomplished what you need, I believe. (It is better than bumppercent 100, which would maybe run an estimate for level N+1, which will later be decided as not to be good -- too much waste of time + machine load). Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Bijnens Sent: 11 October 2007 10:07 To: Amanda List Subject: Re: RE exclusions On 2007-10-11 10:35, Johan Booysen wrote: Thanks fo your reply. My understanding (as far as that goes) has always been that amanda can only do full and incremental backups? ?? ...only... ?? What other kind of backup are you hinting at? If you mean a http://www.backup4all.com/differential-backup.php;, then that's just an incremental level 1, which you can configure by setting e.g. bumppercent 100, or by setting bumpdays 9 (the latter one assumes you do run at least one other full backup within the next 273 years :-) ). I've been doing full backups because until now we've had the capacity to do that. If I switch to the way amanda should really work, then does that not mean that I'll get full and incremental backups, which will make the restore process more cumbersome in terms of the number of tapes needed for a restore? Yes, but not so complicated that a restore becomes an gigantic task. Moreover, then chance to need to restore a recently modified file is much larger than files that are never changed. And in that case restore from an incremental is much faster. How else would you like to solve the problem of too much data to fit on a tape? (besides removing the dead files.) I'm still using amanda 2.4.4. Will appreciate your advice on this. - - -- *From:* Cyrille Bollu [mailto:[EMAIL PROTECTED] *Sent:* 10 October 2007 16:57 *To:* Johan Booysen *Cc:* amanda-users@amanda.org; [EMAIL PROTECTED] *Subject:* RE exclusions At first sight it looks very easy: You are currently only doing full-daily backups. So, switch to regular incremental/differential backups and you'll be fine (No need to ask people doing tar files...) Also, Amanda has all the features you need to keep track of where your files have been backuped. (eg: index yes in amanda.conf, amrecover, amtoc,...) What I want to do now is continue doing full backups every night, but exclude any data that will have been backed up to the monthly archive tape. IMHO, you are describing a differential backup scheme here. Cyrille -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED]
Re: sendsize finishes, planner doesn't notice...
Jean-Louis Martineau [EMAIL PROTECTED] writes: It's weird. Do you have an amdump log file or just amdump.1? The only way to get this is if you killed amanda process on the server, maybe a server crash. Do you still have amanda process running on the server? I do now. I started amanda off Tuesday night at Tue Oct 9 22:48:34 2007. According the /var/log/amanda/amandad/amandad.20071009224834.debug file: amandad: time 21604.147: pid 26218 finish time Wed Oct 10 04:48:39 2007 According to sendsize.20071009224835.debug: amanda2:/var/log/amanda/client/offsite# tail sendsize.20071009224835.debug errmsg is /usr/local/libexec/runtar exited with status 1: see /var/log/amanda/client/offsite/sendsize.20071009224835.debug sendsize[26687]: time 37138.237: done with amname /permabit/user/uz dirname /permabit/user spindle -1 sendsize[26379]: time 37823.330: Total bytes written: 541649408000 (505GiB, 14MiB/s) sendsize[26379]: time 37823.453: . sendsize[26379]: time 37823.453: estimate time for /permabit/user/eh level 0: 37823.251 sendsize[26379]: time 37823.453: estimate size for /permabit/user/eh level 0: 528954500 KB sendsize[26379]: time 37823.453: waiting for runtar /permabit/user/eh child sendsize[26379]: time 37823.453: after runtar /permabit/user/eh wait errmsg is /usr/local/libexec/runtar exited with status 1: see /var/log/amanda/client/offsite/sendsize.20071009224835.debug sendsize[26379]: time 37823.537: done with amname /permabit/user/eh dirname /permabit/user spindle -1 So, sendsize claims to be done, yet planner doesn't think so: planner: time 16531.383: got partial result for host amanda2 disk \ /permabit/user/uz: 0 - -2K, -1 - -2K, -1 - -2K [...] planner: time 16531.384: got partial result for host amanda2 disk \ /permabit/user/eh: 0 - -2K, -1 - -2K, -1 - -2K amdump is currently still running, amandad has finished, but we're still waiting for estimates which will never arrive. I also find it disturbing that the debug log I'm looking at, sendsize.20071009224835.debug, tells me to look at the log I'm looking at for further information: errmsg is /usr/local/libexec/runtar exited with status 1: see \ /var/log/amanda/client/offsite/sendsize.20071009224835.debug Any idea why amandad is dying before sending the estimate data back to the planner? My etimeout is currently set to: # grep timeout /etc/amanda/offsite/amanda.conf etimeout 72000 # number of seconds per filesystem for estimates. dtimeout 72000 # number of idle seconds before a dump is aborted. ctimeout30 # maximum number of seconds that amcheck waits amanda2:/var/log/amanda/server/offsite# su - backup -c 'amadmin offsite config' | grep -i timeout ETIMEOUT 72000 DTIMEOUT 72000 CTIMEOUT 30 amanda2:/var/log/amanda/server/offsite# /usr/local/sbin/amgetconf offsite etimeout 72000 su - backup -c 'amadmin offsite version' build: VERSION=Amanda-2.5.2p1 BUILT_DATE=Tue Sep 4 15:45:27 EDT 2007 BUILT_MACH=Linux amanda2 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 GNU/Linux CC=gcc-4.2 CONFIGURE_COMMAND='./configure' '--prefix=/usr/local' '--enable-shared' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-index-server=localhost' '--with-user=backup' '--with-group=backup' '--with-bsd-security' '--with-amandahosts' '--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' '--with-tcpportrange=5,50100' '--with-udpportrange=840,860' '--with-maxtapeblocksize=256' '--with-ssh-security' paths: bindir=/usr/local/bin sbindir=/usr/local/sbin libexecdir=/usr/local/libexec mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=UNDEF RESTORE=UNDEF VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF SAMBA_CLIENT=UNDEF GNUTAR=/bin/tar COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip LPRCMD=/usr/bin/lpr MAILER=/usr/bin/Mail listed_incr_dir=/var/lib/amanda/gnutar-lists defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 DEFAULT_TAPE_SERVER=localhost HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc Am I missing something extremely obvious? I've been using amanda for over a decade, and I can't figure out why she's behaving like this. If there's any more information you need in order to help me figure this out, please let me know, the suspense here is killing me :) -- Thanks, Paul
Re: sendsize finishes, planner doesn't notice...
The seems a bit similar to firewall issues we had a while back --- the sendsize estimate took long enough that the connection FROM the server was closed. The firewall only allowed connections made by the server, or replies back through the same connection... and needed to be opened for the client to start a new connection back TO the server, when the estimate took over a certain amount of time. My understanding of it may be poor, but perhaps this will jog somebody's mind Deb At 3:39 PM -0400 10/11/07, Paul Lussier wrote: Jean-Louis Martineau [EMAIL PROTECTED] writes: It's weird. Do you have an amdump log file or just amdump.1? The only way to get this is if you killed amanda process on the server, maybe a server crash. Do you still have amanda process running on the server? I do now. I started amanda off Tuesday night at Tue Oct 9 22:48:34 2007. According the /var/log/amanda/amandad/amandad.20071009224834.debug file: amandad: time 21604.147: pid 26218 finish time Wed Oct 10 04:48:39 2007 According to sendsize.20071009224835.debug: amanda2:/var/log/amanda/client/offsite# tail sendsize.20071009224835.debug errmsg is /usr/local/libexec/runtar exited with status 1: see /var/log/amanda/client/offsite/sendsize.20071009224835.debug sendsize[26687]: time 37138.237: done with amname /permabit/user/uz dirname /permabit/user spindle -1 sendsize[26379]: time 37823.330: Total bytes written: 541649408000 (505GiB, 14MiB/s) sendsize[26379]: time 37823.453: . sendsize[26379]: time 37823.453: estimate time for /permabit/user/eh level 0: 37823.251 sendsize[26379]: time 37823.453: estimate size for /permabit/user/eh level 0: 528954500 KB sendsize[26379]: time 37823.453: waiting for runtar /permabit/user/eh child sendsize[26379]: time 37823.453: after runtar /permabit/user/eh wait errmsg is /usr/local/libexec/runtar exited with status 1: see /var/log/amanda/client/offsite/sendsize.20071009224835.debug sendsize[26379]: time 37823.537: done with amname /permabit/user/eh dirname /permabit/user spindle -1 So, sendsize claims to be done, yet planner doesn't think so: planner: time 16531.383: got partial result for host amanda2 disk \ /permabit/user/uz: 0 - -2K, -1 - -2K, -1 - -2K [...] planner: time 16531.384: got partial result for host amanda2 disk \ /permabit/user/eh: 0 - -2K, -1 - -2K, -1 - -2K amdump is currently still running, amandad has finished, but we're still waiting for estimates which will never arrive. I also find it disturbing that the debug log I'm looking at, sendsize.20071009224835.debug, tells me to look at the log I'm looking at for further information: errmsg is /usr/local/libexec/runtar exited with status 1: see \ /var/log/amanda/client/offsite/sendsize.20071009224835.debug Any idea why amandad is dying before sending the estimate data back to the planner? My etimeout is currently set to: # grep timeout /etc/amanda/offsite/amanda.conf etimeout 72000 # number of seconds per filesystem for estimates. dtimeout 72000 # number of idle seconds before a dump is aborted. ctimeout30 # maximum number of seconds that amcheck waits amanda2:/var/log/amanda/server/offsite# su - backup -c 'amadmin offsite config' | grep -i timeout ETIMEOUT 72000 DTIMEOUT 72000 CTIMEOUT 30 amanda2:/var/log/amanda/server/offsite# /usr/local/sbin/amgetconf offsite etimeout 72000 su - backup -c 'amadmin offsite version' build: VERSION=Amanda-2.5.2p1 BUILT_DATE=Tue Sep 4 15:45:27 EDT 2007 BUILT_MACH=Linux amanda2 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 GNU/Linux CC=gcc-4.2 CONFIGURE_COMMAND='./configure' '--prefix=/usr/local' '--enable-shared' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-index-server=localhost' '--with-user=backup' '--with-group=backup' '--with-bsd-security' '--with-amandahosts' '--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' '--with-tcpportrange=5,50100' '--with-udpportrange=840,860' '--with-maxtapeblocksize=256' '--with-ssh-security' paths: bindir=/usr/local/bin sbindir=/usr/local/sbin libexecdir=/usr/local/libexec mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=UNDEF RESTORE=UNDEF VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF SAMBA_CLIENT=UNDEF GNUTAR=/bin/tar COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip LPRCMD=/usr/bin/lpr MAILER=/usr/bin/Mail listed_incr_dir=/var/lib/amanda/gnutar-lists defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 DEFAULT_TAPE_SERVER=localhost HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID
Re: sendsize finishes, planner doesn't notice...
Paul Lussier wrote: Jean-Louis Martineau [EMAIL PROTECTED] writes: It's weird. Do you have an amdump log file or just amdump.1? The only way to get this is if you killed amanda process on the server, maybe a server crash. Do you still have amanda process running on the server? I do now. I started amanda off Tuesday night at Tue Oct 9 22:48:34 2007. According the /var/log/amanda/amandad/amandad.20071009224834.debug file: amandad: time 21604.147: pid 26218 finish time Wed Oct 10 04:48:39 2007 According to sendsize.20071009224835.debug: amanda2:/var/log/amanda/client/offsite# tail sendsize.20071009224835.debug errmsg is /usr/local/libexec/runtar exited with status 1: see /var/log/amanda/client/offsite/sendsize.20071009224835.debug sendsize[26687]: time 37138.237: done with amname /permabit/user/uz dirname /permabit/user spindle -1 sendsize[26379]: time 37823.330: Total bytes written: 541649408000 (505GiB, 14MiB/s) sendsize[26379]: time 37823.453: . sendsize[26379]: time 37823.453: estimate time for /permabit/user/eh level 0: 37823.251 sendsize[26379]: time 37823.453: estimate size for /permabit/user/eh level 0: 528954500 KB sendsize[26379]: time 37823.453: waiting for runtar /permabit/user/eh child sendsize[26379]: time 37823.453: after runtar /permabit/user/eh wait errmsg is /usr/local/libexec/runtar exited with status 1: see /var/log/amanda/client/offsite/sendsize.20071009224835.debug sendsize[26379]: time 37823.537: done with amname /permabit/user/eh dirname /permabit/user spindle -1 So, sendsize claims to be done, yet planner doesn't think so: sendsize doesn't claims to be done, I don't see the finish time' line at the of the log. Is it still running? planner: time 16531.383: got partial result for host amanda2 disk \ /permabit/user/uz: 0 - -2K, -1 - -2K, -1 - -2K [...] planner: time 16531.384: got partial result for host amanda2 disk \ /permabit/user/eh: 0 - -2K, -1 - -2K, -1 - -2K amdump is currently still running, amandad has finished, but we're still waiting for estimates which will never arrive. I also find it disturbing that the debug log I'm looking at, sendsize.20071009224835.debug, tells me to look at the log I'm looking at for further information: errmsg is /usr/local/libexec/runtar exited with status 1: see \ /var/log/amanda/client/offsite/sendsize.20071009224835.debug Any idea why amandad is dying before sending the estimate data back to the planner? My etimeout is currently set to: amandad didn't dye, its log show it finished correctly. Am I missing something extremely obvious? I've been using amanda for over a decade, and I can't figure out why she's behaving like this. If there's any more information you need in order to help me figure this out, please let me know, the suspense here is killing me :) If sendsize is not running, it's because it crashed. I don't understand why amandad finish before sendsize, can you post complete amandad and sendsize debug files. Jean-Louis
