Amanda 3.1.2 on Solaris 10x86.
Occasionally we see this failure, even when the prior run
ends cleanly.
I'm not sure how amanda handles it,
does sit fail to create the snapshot ?
does it destroy and then create a new snapshot ?
It did successfully backup the DLE.
NOTES:
planner:
Brian Cuttler wrote:
Amanda 3.1.2 on Solaris 10x86.
Occasionally we see this failure, even when the prior run
ends cleanly.
Can you find in the debug files why the destroy failed in the prior runs?
I'm not sure how amanda handles it,
does sit fail to create the snapshot ?
does it
On Fri, Nov 05, 2010 at 10:15:55AM -0400, Jean-Louis Martineau wrote:
Brian Cuttler wrote:
Amanda 3.1.2 on Solaris 10x86.
Occasionally we see this failure, even when the prior run
ends cleanly.
Can you find in the debug files why the destroy failed in the prior runs?
I'm not sure how
amdump: datestamp 20101105
amdump: starttime 20101105115136
amdump: starttime-locale-independent 2010-11-05 11:51:36 CDT
planner: pid 3659 executable /usr/libexec/amanda/planner version 3.2.0
planner: build: VERSION=Amanda-3.2.0
planner:BUILT_DATE=Mon Oct 18 09:20:30 PDT 2010 BUILT_MACH
Rhys Rhaven wrote:
Using amanda 3.2.0 on everything. I have 2 hosts and a server
currently. 1 host and the server are ubuntu 10.04 and the other host
(that I'm having issues with) is 8.04.
I can run amdump for each host individually with no problem. Running
amdump for the config (daily) will
Sorry bout that.
amdump: start at Fri Nov 5 00:00:01 CDT 2010
amdump: datestamp 20101105
amdump: starttime 2010110501
amdump: starttime-locale-independent 2010-11-05 00:00:01 CDT
driver: pid 3102 executable /usr/libexec/amanda/driver version 3.2.0
planner: pid 3101 executable /usr/libexec
Hi Rhys,
It's a bug, can you try the attached patch?
Jean-Louis
Rhys Rhaven wrote:
Using amanda 3.2.0 on everything. I have 2 hosts and a server
currently. 1 host and the server are ubuntu 10.04 and the other host
(that I'm having issues with) is 8.04.
I can run amdump for each host