Was the new directory (filesystem) that you added bigger than the ones that were working?
I had a problem with using tar on a big filesystem and the estimate would always time-out.
if the new disk is bigger by a great deal try doubleing the etimeout value in the amanda.conf file. I had to do this many, 3, time before amanda would backup a nearly full 45 gig filesystem.
I hope this helps
chris
Matthew Boeckman wrote:
No result for estimate level 0!
Did the planner asker for level 0 estimate? (REQ packet form amandad.debug)
guess I'm not sure I know how to answer that question, but some output from amandad.debug that my answer it for me:
--------
Amanda 2.4 REQ HANDLE 000-000549D0 SEQ 1038837189
SECURITY USER amanda
SERVICE sendsize
OPTIONS maxdumps=1;hostname=ultra;
GNUTAR /webhome/bkup1 2 2002:11:18:8:5:49 -1 exclude-list=/home/amanda/bkup1
--------
amandad: running service "/usr/local/amanda/libexec/sendsize"
amandad: got packet:
----
Amanda 2.4 REQ HANDLE 000-000549D0 SEQ 1038837189
SECURITY USER amanda
SERVICE sendsize
OPTIONS maxdumps=1;hostname=ultra;
GNUTAR /webhome/bkup1 2 2002:11:18:8:5:49 -1 exclude-list=/home/amanda/bkup1
----
amandad: received dup P_REQ packet, ACKing it
sending ack:
----
Amanda 2.4 ACK HANDLE 000-000549D0 SEQ 1038837189
----
amandad: sending REP packet:
----
Amanda 2.4 REP HANDLE 000-000549D0 SEQ 1038837189
OPTIONS maxdumps=1;
/webhome/bkup1 2 SIZE 12408030
----
If not, WHY? look into the amdump log file.can't find any amdump log file!What's your dumptype? (amadmin <conf> disklist ultra /webhome/bkup1)bash-2.03$ amadmin csd disklist ultra /webhome/bkup1 line 18: host ultra: interface default disk /webhome/bkup1: program "GNUTAR" exclude list "/home/amanda/bkup1" priority 2 dumpcycle 7 maxdumps 1 strategy STANDARD compress NONE auth BSD kencrypt NO holdingdisk YES record YES index YES skip-incr NO skip-full NOWhich release of amanda?amanda 2.4.2 on Solaris7/SPARCJean-Louis
