|
Re: problem with amdump
2004-05-06 10:49:02
Here is the sendsize debug file...
sendsize: debug 1 pid 14004 ruid 33 euid 33: start at Thu May 6 15:54:31
2004
sendsize: version 2.4.4p2
sendsize[14006]: time 0.003: calculating for amname '/home/noe', dirname
'/home/noe', spindle -1
sendsize[14006]: time 0.003: getting size via gnutar for /home/noe level 0
sendsize[14006]: opening
/usr/local/var/amanda/gnutar-lists/amandatux.int-evry.fr_home_noe_0.new:
No such file or directory
sendsize[14006]: time 0.004: done with amname '/home/noe', dirname
'/home/noe', spindle -1
sendsize[14004]: time 0.004: waiting for any estimate child: 1 running
sendsize[14004]: time 0.004: child 14006 terminated normally
sendsize: time 0.004: pid 14004 finish time Thu May 6 15:54:31 2004
I created the directory "/usr/local/var/amanda/gnutar-lists/ " which
formerly I had on another place, and tried again and everything works
well know thanks for help Jaoshua.
Joshua Baker-LePain wrote:
On Thu, 6 May 2004 at 4:08pm, nejat onay erkose wrote
DISK planner amandatux.int-evry.fr /home/noe
START planner date 20040506
INFO planner Adding new disk amandatux.int-evry.fr:/home/noe.
START driver date 20040506
FAIL planner amandatux.int-evry.fr /home/noe 20040506 0 [disk /home/noe,
all estimate failed]
FINISH planner date 20040506
WARNING driver WARNING: got empty schedule from planner
And what does sendsize*debug and/or amandad*debug on the client have to
say?
... and when I run amrecover I got the below message stating that it
cannot find any log files for the date.
Err, if you haven't backed anything up yet, what files would there be to
recover?
|
|
|
