Justin!
> The first one started to occur after rebuilding my Tape Backup Server after
> a Hard Disk Crash. I changed it from a SCSI disk to a IDE disk. Now when
> ever it goes to dump any of the file systems on that system (sol), it gives
> this in the AMDUMP report:
> sol hda1 lev 0 FAILED [disk hda1 offline on sol?]
Have you looked in /tmp/amanda/*.debug? Every now and then things will
show up there. Do this on the backup and the client machine.
> ERROR: sol: [can not access hda1 (hda1): No such file or directory]
Shouldn't it be /dev/hda1?
> And this is how it is configured in disklist:
>
> sol hda1 comp-root-tar
> The second error I am not to sure about:
> tigereye hda4 lev 0 FAILED [can't switch to incremental dump]
There is no lock file. A default configuration will have the reserve
parameter set to 100 per cent. When a dump fails, AMANDA will dump it to
disk UNLESS the holding disk has less free space than that specified in
the reserve parameter. If this is the case, it will bump the dump at
least one level. In AMANDA parlance this is called "degraded dumps" (I
think).
You could set the reserve parameter to something lower. I have a large
holding disk on my setup where I can actually stack 5 full days' backups
into 85% of the disk space, so I only reserve 25%.
Look in [amanda source directory]/examples/amanda.conf.in for another
explanation of reserve.
DL
--
GOD SAVE AMERICA!
- because President Bush, the Second Will Not!
