I'm not sure what the point of posting the whole amdump.1 file was,
but since you did, here's the remainder of the analysis:
$ grep 'got result' amdump.1
got result for host admin1.corp.walid.com disk sda2: 0 -> 304817K, 1 -> 303921K, 2
-> 303881K
...
got result for host admin1.corp.walid.com disk sda10: 0 -> 4881376K, 1 -> 3000789K,
-1 -> -1K
...
got result for host sundev1.corp.walid.com disk c0t0d0s7: 0 -> 5255527K, 1 ->
951372K, -1 -> -1K
...
So, as I guessed, each of these needed more than 140 MBytes:
sda2: 303921K
sda10: 3000789K
c0t0d0s7: 951372K
and thus there was not enough holding disk space for any of them after
150 MBytes had already been used up.
So this means you need at least 4.4 GBytes of holding disk space for
each run (I'd make it 5+). You have ~6 GBytes free in /home so you can
only fit one run before you'll have to do an amflush (and that assumes
you don't mind using up all that space).
Another problem is that your holding disk is in /home, a.k.a. c0t0d0s7.
As I mentioned before, you can't do that. Since you're being forced to
only use the holding disk, you could change to using GNU tar and excluding
the holding disk area from the backup of /home. Otherwise you'll be
backing up the holding disk at the same time the holding disk is growing.
Note that at 5 GBytes per no-tape run, and assuming you added a large
enough holding disk, you'll only fit four or five runs on a 20+ GByte tape
(you'll never get 40 GBytes on those tapes -- only marketing folks live
in that fantasy world). In other words, you'll be able to run amdump
four or five times, then will have to use amflush. And since you only
have two tapes, you'll also have to do the immediate "amadmin force"
and amdump to do the level 0's.
I think you and your management need to rethink your whole plan.
You either need to add a large, very reliable, dedicated holding disk or
buy enough tapes to make a real Amanda run each day. Trying to shoehorn
your data needs into what you have is clearly not working. And it is
most definitely not safe, which is the one thing you want your backup
system to be.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
