On Mar 10, 2005, at 11:32 PM, Jon LaBadie wrote:
Do you have the "record yes" property set (I suspect you do)
and is the appropriate dumpdates or amandates file created and
writable by amanda? Perhaps it is not able to record when the
last level X was done.
D'OH!
I had slipped a 'record no' in th
On Thu, Mar 10, 2005 at 08:13:42PM -0500, Marc N. Cannava wrote:
> Hi all,
>
> I've been using Amanda for a while with no issue.
>
> I recently moved from RH9 to Gentoo and re-installed amanda with the
> latest version available in the ebuild tree (amanda 2.4.4_p3). Using my
> same config files
Ah!! I found the log.
This is what Amanda said from the last run:
taper: read label `Homenet18' date `X'
taper: wrote label `Homenet18' date `20050310'
planner: time 231.726: got result for host ziyal disk /data2/public: 0
-> 2071100K, 1 -> 2071100K, 2 -> 2071100K
planner: time 231.726: got result
On Mar 10, 2005, at 8:36 PM, Kevin Dalley wrote:
Do you have something like this in your amdump file:
planner: time 1817.635: got result for host condor disk //bunting/e$:
0 -> 5524252K, 1 -> 108113K, 2 -> 108113K
You know, I just realized that Amanda isn't logging where I expect
(/tmp/amanda).
Do you have something like this in your amdump file:
planner: time 1817.635: got result for host condor disk //bunting/e$: 0 ->
5524252K, 1 -> 108113K, 2 -> 108113K
It should verify that it calculates the level 0 and level 1 backups.
Is the level 0 actually written entirely to disk (or tape).
Hi all,
I've been using Amanda for a while with no issue.
I recently moved from RH9 to Gentoo and re-installed amanda with the
latest version available in the ebuild tree (amanda 2.4.4_p3). Using my
same config files and backing up to disk (using chg-disk).
Very, very odd problem now: No matter
